Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d330f156e785b9448e13f928b5880b649bea2de2917b7e26f5aa8e8afd32ef6

Tx prefix hash: c90a2b5bac3c61ac3b77d8d6c7e02d26d8c87f23077f96bbaddad82ad2404e35
Tx public key: 4bcc971a02fe036c196d9c42577122fa8068881a7f36c21458cec9a790104403
Timestamp: 1736500444 Timestamp [UCT]: 2025-01-10 09:14:04 Age [y:d:h:m:s]: 00:068:12:51:47
Block: 1194214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48781 RingCT/type: yes/0
Extra: 014bcc971a02fe036c196d9c42577122fa8068881a7f36c21458cec9a7901044030211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 453b807b4f2b1df568ab7e6a9276532a948275bad64d67da07e60bd627ce7fb2 0.600000000000 1680781 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": 1194224, "vin": [ { "gen": { "height": 1194214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "453b807b4f2b1df568ab7e6a9276532a948275bad64d67da07e60bd627ce7fb2" } } ], "extra": [ 1, 75, 204, 151, 26, 2, 254, 3, 108, 25, 109, 156, 66, 87, 113, 34, 250, 128, 104, 136, 26, 127, 54, 194, 20, 88, 206, 201, 167, 144, 16, 68, 3, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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