Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61f503b6a47c5d6227e3be39b0ca140f0fe75a4c9fa3a3bdaec29e82f80994b0

Tx prefix hash: f2350a3e51b62fc726982424d4cdee09d180f44fc7d053319b4e91df697b9d67
Tx public key: e81c942f38cedc72c86aeb10eeb6386177d1d26460ce691c6e02be371d0cf78a
Timestamp: 1712791784 Timestamp [UCT]: 2024-04-10 23:29:44 Age [y:d:h:m:s]: 01:203:22:13:52
Block: 997769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404433 RingCT/type: yes/0
Extra: 01e81c942f38cedc72c86aeb10eeb6386177d1d26460ce691c6e02be371d0cf78a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee723b406e172e2398c3a059ce2a80c25000f2f330b692ee4d23952bd5f92dce 0.600000000000 1458203 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": 997779, "vin": [ { "gen": { "height": 997769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee723b406e172e2398c3a059ce2a80c25000f2f330b692ee4d23952bd5f92dce" } } ], "extra": [ 1, 232, 28, 148, 47, 56, 206, 220, 114, 200, 106, 235, 16, 238, 182, 56, 97, 119, 209, 210, 100, 96, 206, 105, 28, 110, 2, 190, 55, 29, 12, 247, 138, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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