Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc44bbfd35995c35b622fa2c866bac88123ef871af91a5c3a9b92d780587205

Tx prefix hash: e1835c7b404a02606dc46e165118b3a9799e41d2b3e34d079c0b5de2bb567399
Tx public key: 473c45baea20644d0e12836f099bf9012975d142f02acc674174a16b6dbf1b4c
Timestamp: 1709425829 Timestamp [UCT]: 2024-03-03 00:30:29 Age [y:d:h:m:s]: 01:055:08:11:18
Block: 969896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300567 RingCT/type: yes/0
Extra: 01473c45baea20644d0e12836f099bf9012975d142f02acc674174a16b6dbf1b4c0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc80aea2c892656e3d1e6db8736dd4e6b8843878fd90645c801cdc0a3b41a242 0.600000000000 1429745 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": 969906, "vin": [ { "gen": { "height": 969896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc80aea2c892656e3d1e6db8736dd4e6b8843878fd90645c801cdc0a3b41a242" } } ], "extra": [ 1, 71, 60, 69, 186, 234, 32, 100, 77, 14, 18, 131, 111, 9, 155, 249, 1, 41, 117, 209, 66, 240, 42, 204, 103, 65, 116, 161, 107, 109, 191, 27, 76, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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