Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd22bcef733b5f506f098aa95f47b58ebdbfb6d238899aba51081454d98ea55b

Tx prefix hash: dd7c385fc6ac2a38e0a4b0e67da3b8b85d8eaa6f858343ed0ffbea28c806611f
Tx public key: 099e2cb630523f372b740774fda02cac7b0f0751ac5a68b276fd9179385229b0
Timestamp: 1736140744 Timestamp [UCT]: 2025-01-06 05:19:04 Age [y:d:h:m:s]: 00:091:21:36:52
Block: 1191251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65435 RingCT/type: yes/0
Extra: 01099e2cb630523f372b740774fda02cac7b0f0751ac5a68b276fd9179385229b00211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a6f5405c712bf6ae7d7c1a1784709703474fad0d36a9bd281d1ce176e94889e 0.600000000000 1677774 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": 1191261, "vin": [ { "gen": { "height": 1191251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a6f5405c712bf6ae7d7c1a1784709703474fad0d36a9bd281d1ce176e94889e" } } ], "extra": [ 1, 9, 158, 44, 182, 48, 82, 63, 55, 43, 116, 7, 116, 253, 160, 44, 172, 123, 15, 7, 81, 172, 90, 104, 178, 118, 253, 145, 121, 56, 82, 41, 176, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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