Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee10c43b85ef40e6c2d83388eaac31ee4d5f61b808e91c2cc05150f6378bd646

Tx prefix hash: c6d8ef11822cfb3e7dae0f439ae000d240610222697feacd951d9b2f938e74b3
Tx public key: 8cb0cfde8d3b06d6958527179d05fe7926220d4e907ea583145b91ab7e508c39
Timestamp: 1704367970 Timestamp [UCT]: 2024-01-04 11:32:50 Age [y:d:h:m:s]: 01:126:22:19:49
Block: 927971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351823 RingCT/type: yes/0
Extra: 018cb0cfde8d3b06d6958527179d05fe7926220d4e907ea583145b91ab7e508c390211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f28eee2331665907afcc728626c86b8e71d703c63d209dfef3b1203691c061ce 0.600000000000 1385819 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": 927981, "vin": [ { "gen": { "height": 927971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f28eee2331665907afcc728626c86b8e71d703c63d209dfef3b1203691c061ce" } } ], "extra": [ 1, 140, 176, 207, 222, 141, 59, 6, 214, 149, 133, 39, 23, 157, 5, 254, 121, 38, 34, 13, 78, 144, 126, 165, 131, 20, 91, 145, 171, 126, 80, 140, 57, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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