Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f516272c6fd44cfd54a4dbf86d2043714cd06c1d6730d9a40a4fe56b2b8cb50a

Tx prefix hash: b693e0f0928f70db9a116947d8787d33474777517ee0ba4e47f83c97eb37cd9f
Tx public key: abbe6341e73b6fa2a253517e1def3e3aa8bdefbaf2f721c587fe98021026c5fd
Timestamp: 1721578739 Timestamp [UCT]: 2024-07-21 16:18:59 Age [y:d:h:m:s]: 00:240:18:09:29
Block: 1070637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172005 RingCT/type: yes/0
Extra: 01abbe6341e73b6fa2a253517e1def3e3aa8bdefbaf2f721c587fe98021026c5fd021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0de1f2fbd68d579533138e2219f38a22ae552634d649d5044bb8bc1619970a16 0.600000000000 1542554 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": 1070647, "vin": [ { "gen": { "height": 1070637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0de1f2fbd68d579533138e2219f38a22ae552634d649d5044bb8bc1619970a16" } } ], "extra": [ 1, 171, 190, 99, 65, 231, 59, 111, 162, 162, 83, 81, 126, 29, 239, 62, 58, 168, 189, 239, 186, 242, 247, 33, 197, 135, 254, 152, 2, 16, 38, 197, 253, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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