Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dfc95fd8eb227901a67ebd05814a7523319676af94bd19de971fd114429d5b1

Tx prefix hash: 44a9639d6a5749dfc7a0c352111c02b41b32e5d149fb2080e4eab2f087e703d4
Tx public key: 0db78f931813c2cfae3ee08ba0c298f75d6cb401a2186bab0fa7853e7aaaca58
Timestamp: 1742294124 Timestamp [UCT]: 2025-03-18 10:35:24 Age [y:d:h:m:s]: 00:318:19:02:00
Block: 1241924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225474 RingCT/type: yes/0
Extra: 010db78f931813c2cfae3ee08ba0c298f75d6cb401a2186bab0fa7853e7aaaca580211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a8ff066fc1ba849529cefed9da64178b498528d2cdb0eadc315e7e09a0a1356 0.600000000000 1728897 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": 1241934, "vin": [ { "gen": { "height": 1241924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a8ff066fc1ba849529cefed9da64178b498528d2cdb0eadc315e7e09a0a1356" } } ], "extra": [ 1, 13, 183, 143, 147, 24, 19, 194, 207, 174, 62, 224, 139, 160, 194, 152, 247, 93, 108, 180, 1, 162, 24, 107, 171, 15, 167, 133, 62, 122, 170, 202, 88, 2, 17, 0, 0, 0, 2, 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