Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2af7b342a398ad2191b5460ee152d0b68b3eccc64a83c9c3c1997e37d4993fb0

Tx prefix hash: 5b868af4e335801305e964fc051cf15794b0a01ddb3ba3ec51980e98d042d704
Tx public key: 6be78c0f4ec18ab91bb0d2a4d1a5c82c94d2f1f763e76e9f3d9e71e16c558b8f
Timestamp: 1711158645 Timestamp [UCT]: 2024-03-23 01:50:45 Age [y:d:h:m:s]: 00:361:08:56:02
Block: 984277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258378 RingCT/type: yes/0
Extra: 016be78c0f4ec18ab91bb0d2a4d1a5c82c94d2f1f763e76e9f3d9e71e16c558b8f0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ff05a5b98f0b0579e931f070f39c028d075a3b687e3e831608a363e7eeee370 0.600000000000 1444446 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": 984287, "vin": [ { "gen": { "height": 984277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ff05a5b98f0b0579e931f070f39c028d075a3b687e3e831608a363e7eeee370" } } ], "extra": [ 1, 107, 231, 140, 15, 78, 193, 138, 185, 27, 176, 210, 164, 209, 165, 200, 44, 148, 210, 241, 247, 99, 231, 110, 159, 61, 158, 113, 225, 108, 85, 139, 143, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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