Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d807d1155232d17fcf1fe6c0fc75bfde236ce38fe723363b4285b49ee931aa1

Tx prefix hash: e7418b050125dcf4f55e5cf64870d20f028dd18c300d2afafb59a158bcba5919
Tx public key: 6f974ddeab0ee1515ddef91f76b46a6aa3f3d9ea2cda596b31aef8053a559701
Timestamp: 1734381107 Timestamp [UCT]: 2024-12-16 20:31:47 Age [y:d:h:m:s]: 00:093:01:34:04
Block: 1176693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66302 RingCT/type: yes/0
Extra: 016f974ddeab0ee1515ddef91f76b46a6aa3f3d9ea2cda596b31aef8053a559701021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d0be81c847a2e8cb73efce69ad986319affe00dea0a2a7fc3da759eac020c49 0.600000000000 1663052 of 15

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": 1176703, "vin": [ { "gen": { "height": 1176693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d0be81c847a2e8cb73efce69ad986319affe00dea0a2a7fc3da759eac020c49" } } ], "extra": [ 1, 111, 151, 77, 222, 171, 14, 225, 81, 93, 222, 249, 31, 118, 180, 106, 106, 163, 243, 217, 234, 44, 218, 89, 107, 49, 174, 248, 5, 58, 85, 151, 1, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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