Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82fd8848dc9b5ca6c78efd5b971b29e7075ebd0bc6293039f5a8bb3464d49be4

Tx prefix hash: 960ba77b3e234094207d0d5a0e26365864e7b398777b777f5f5b806b4583fae9
Tx public key: 6873ef5f4d0b1bb59b6712fc59ecc7b09ed108fbf7b8f22f5ecd0c400308d87d
Timestamp: 1758645848 Timestamp [UCT]: 2025-09-23 16:44:08 Age [y:d:h:m:s]: 00:104:03:33:43
Block: 1374825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74601 RingCT/type: yes/0
Extra: 016873ef5f4d0b1bb59b6712fc59ecc7b09ed108fbf7b8f22f5ecd0c400308d87d021100000008ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb8782345e28c0b530f75f801aaea082d0c220654d6cc409347e096def974fab 0.600000000000 1862910 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": 1374835, "vin": [ { "gen": { "height": 1374825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb8782345e28c0b530f75f801aaea082d0c220654d6cc409347e096def974fab" } } ], "extra": [ 1, 104, 115, 239, 95, 77, 11, 27, 181, 155, 103, 18, 252, 89, 236, 199, 176, 158, 209, 8, 251, 247, 184, 242, 47, 94, 205, 12, 64, 3, 8, 216, 125, 2, 17, 0, 0, 0, 8, 173, 121, 72, 208, 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