Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28952eba0c8243dd98c8fb0053488a0ff0f0e6a8da039f57a748fbb3cc0722bb

Tx prefix hash: b736f1bd6f631d2917df3440062239f84b68964c8ca9ac78c632ed83a5880100
Tx public key: bfd4536debda7f2d9adba6b83f90919feeb0c19461a72ccca5b1d03d8796c3d7
Timestamp: 1764276670 Timestamp [UCT]: 2025-11-27 20:51:10 Age [y:d:h:m:s]: 00:062:17:07:15
Block: 1421506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44714 RingCT/type: yes/0
Extra: 01bfd4536debda7f2d9adba6b83f90919feeb0c19461a72ccca5b1d03d8796c3d70211000000058ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95c0aca04fe78f13b2ac65fde3ba6dd50c7cb341371990a174273fc35f0d1c36 0.600000000000 1910063 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": 1421516, "vin": [ { "gen": { "height": 1421506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95c0aca04fe78f13b2ac65fde3ba6dd50c7cb341371990a174273fc35f0d1c36" } } ], "extra": [ 1, 191, 212, 83, 109, 235, 218, 127, 45, 154, 219, 166, 184, 63, 144, 145, 159, 238, 176, 193, 148, 97, 167, 44, 204, 165, 177, 208, 61, 135, 150, 195, 215, 2, 17, 0, 0, 0, 5, 140, 235, 127, 9, 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