Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc0efa09056088afe1181077f9cb12de9dc0f89f77fff20e4ef05251ee2fc333

Tx prefix hash: 324b03d53cdc635859de7a9d36264fbec2ff3228a0cc4812f727385cccbca041
Tx public key: 4dc065f17d1321cd5d8573f19f5ce8c699152229f5b906c2520cbaf696969688
Timestamp: 1702797809 Timestamp [UCT]: 2023-12-17 07:23:29 Age [y:d:h:m:s]: 01:033:21:40:07
Block: 914937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285548 RingCT/type: yes/0
Extra: 014dc065f17d1321cd5d8573f19f5ce8c699152229f5b906c2520cbaf696969688021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b6d4f7260497a85cb8c948ea7e0c369ae423ac54aee31b4283db8fa0998c490 0.600000000000 1372297 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": 914947, "vin": [ { "gen": { "height": 914937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b6d4f7260497a85cb8c948ea7e0c369ae423ac54aee31b4283db8fa0998c490" } } ], "extra": [ 1, 77, 192, 101, 241, 125, 19, 33, 205, 93, 133, 115, 241, 159, 92, 232, 198, 153, 21, 34, 41, 245, 185, 6, 194, 82, 12, 186, 246, 150, 150, 150, 136, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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