Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e38f40189799da74df9240b5b82c8fe58f95f500fbf1d420f1c5b70e75566d4a

Tx prefix hash: ccb2ef51de382f354d5aa402c064020799b99e84075e7d6d24ed50b8334e5fa4
Tx public key: d49bd87210f41abbc9fa1aa8131adfecabcef360a3a22dff8cbdb356923f852c
Timestamp: 1728424599 Timestamp [UCT]: 2024-10-08 21:56:39 Age [y:d:h:m:s]: 00:105:09:42:12
Block: 1127391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75324 RingCT/type: yes/0
Extra: 01d49bd87210f41abbc9fa1aa8131adfecabcef360a3a22dff8cbdb356923f852c02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dc5a73221d136f1beacf1e081f392a406c75d54bcae59053244bcc31587a73a 0.600000000000 1610196 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": 1127401, "vin": [ { "gen": { "height": 1127391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dc5a73221d136f1beacf1e081f392a406c75d54bcae59053244bcc31587a73a" } } ], "extra": [ 1, 212, 155, 216, 114, 16, 244, 26, 187, 201, 250, 26, 168, 19, 26, 223, 236, 171, 206, 243, 96, 163, 162, 45, 255, 140, 189, 179, 86, 146, 63, 133, 44, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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