Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2623020636ad94db34adc580d16d5569f6097b66e4d39b8ddf056583a3e15c8

Tx prefix hash: fc2e6c6142be393cd171d8a33cff66771175693754e39f29c18bb9ae654b7853
Tx public key: e5bb06986cb17965daeeb68074621d8a65217cf07f151b7783e51d5be6aa5e84
Timestamp: 1750407213 Timestamp [UCT]: 2025-06-20 08:13:33 Age [y:d:h:m:s]: 00:146:15:41:14
Block: 1308927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102649 RingCT/type: yes/0
Extra: 01e5bb06986cb17965daeeb68074621d8a65217cf07f151b7783e51d5be6aa5e8402110000000bbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85f54d891af9a66cee4d9a0c6b06360c12870c0b2634c5aa2b97ae3219fcae05 0.600000000000 1796542 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": 1308937, "vin": [ { "gen": { "height": 1308927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85f54d891af9a66cee4d9a0c6b06360c12870c0b2634c5aa2b97ae3219fcae05" } } ], "extra": [ 1, 229, 187, 6, 152, 108, 177, 121, 101, 218, 238, 182, 128, 116, 98, 29, 138, 101, 33, 124, 240, 127, 21, 27, 119, 131, 229, 29, 91, 230, 170, 94, 132, 2, 17, 0, 0, 0, 11, 191, 81, 178, 162, 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