Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f735b440de889a2dbc27d03104bdd86ac3f57fce47e0ea0bf7f7cc95cfbd1dd1

Tx prefix hash: a98bb178e4b864e7519d090cd57d37351ca02cf5c066f96c1e9a82d8b7109bd9
Tx public key: 093a628df4900986cb68e9e9df6847f4d2dc50b254c024f56b2d8d552e2dc276
Timestamp: 1701831974 Timestamp [UCT]: 2023-12-06 03:06:14 Age [y:d:h:m:s]: 01:119:02:51:12
Block: 906930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346273 RingCT/type: yes/0
Extra: 01093a628df4900986cb68e9e9df6847f4d2dc50b254c024f56b2d8d552e2dc27602110000000433af99f4000000000000000000

1 output(s) for total of 0.606686594000 dcy

stealth address amount amount idx
00: 09626889aea78daaee5391f70ac4d5affc73805757ddd14a930f62a2aae295ef 0.606686594000 1363891 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 906940, "vin": [ { "gen": { "height": 906930 } } ], "vout": [ { "amount": 606686594, "target": { "key": "09626889aea78daaee5391f70ac4d5affc73805757ddd14a930f62a2aae295ef" } } ], "extra": [ 1, 9, 58, 98, 141, 244, 144, 9, 134, 203, 104, 233, 233, 223, 104, 71, 244, 210, 220, 80, 178, 84, 192, 36, 245, 107, 45, 141, 85, 46, 45, 194, 118, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8