Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03cee2f5bc5a811770a2481a365eb28c16cb8c6df820d8a1c8c358db7658c335

Tx prefix hash: 7333ade7de1a2b454efd6920fe8df3922f5fe986e9a6e06ad891b118fa1b04b5
Tx public key: 1f1a292ea1b92113831a602fd827e26e7b1b01b907db9385acaa9539e9b45b6d
Timestamp: 1748447499 Timestamp [UCT]: 2025-05-28 15:51:39 Age [y:d:h:m:s]: 00:166:05:42:43
Block: 1292868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116483 RingCT/type: yes/0
Extra: 011f1a292ea1b92113831a602fd827e26e7b1b01b907db9385acaa9539e9b45b6d02110000000bdf096e52000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a253d6932608387c85c1f44de273ad433c355077eb51f9e1cf697e91ff1a919 0.600000000000 1780339 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": 1292878, "vin": [ { "gen": { "height": 1292868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a253d6932608387c85c1f44de273ad433c355077eb51f9e1cf697e91ff1a919" } } ], "extra": [ 1, 31, 26, 41, 46, 161, 185, 33, 19, 131, 26, 96, 47, 216, 39, 226, 110, 123, 27, 1, 185, 7, 219, 147, 133, 172, 170, 149, 57, 233, 180, 91, 109, 2, 17, 0, 0, 0, 11, 223, 9, 110, 82, 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