Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c9144cbe0e5e33101fabf55ed4fd3db0239317bdd1bb704ddd1786f77d91ae9

Tx prefix hash: f3a88614be8afe8888110dda8b8b5ffedb69b93ac25c5876e0801d1d09204a9e
Tx public key: 17b38fc5fc45eb8c063ba873da05db5112b968f875d21254e13fadad5eeb735b
Timestamp: 1734436050 Timestamp [UCT]: 2024-12-17 11:47:30 Age [y:d:h:m:s]: 00:177:02:41:07
Block: 1177147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126361 RingCT/type: yes/0
Extra: 0117b38fc5fc45eb8c063ba873da05db5112b968f875d21254e13fadad5eeb735b0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02b5c0b7b2ec0d4380779d634155c83b5f7fb6239b4750ad0598d0b7b224a82f 0.600000000000 1663512 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": 1177157, "vin": [ { "gen": { "height": 1177147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02b5c0b7b2ec0d4380779d634155c83b5f7fb6239b4750ad0598d0b7b224a82f" } } ], "extra": [ 1, 23, 179, 143, 197, 252, 69, 235, 140, 6, 59, 168, 115, 218, 5, 219, 81, 18, 185, 104, 248, 117, 210, 18, 84, 225, 63, 173, 173, 94, 235, 115, 91, 2, 17, 0, 0, 0, 7, 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