Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5f60226a64b5829451ff2f8685bbb4487c8786692c6e557c49ea00e369b9f94

Tx prefix hash: b65778d75f2c5764edd525acc04ae6dfbe0982454d4f859cc1df99187b43e2a0
Tx public key: 6739735d995923695b60bf2af6c8e8638bba19efdf83e73f9a69dc3aa8df4d1d
Timestamp: 1703540779 Timestamp [UCT]: 2023-12-25 21:46:19 Age [y:d:h:m:s]: 01:103:10:18:08
Block: 921096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335031 RingCT/type: yes/0
Extra: 016739735d995923695b60bf2af6c8e8638bba19efdf83e73f9a69dc3aa8df4d1d02110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2328b1bf777e480e9660f57969aa1c268ebec3dd1083c90639be18db5bf156a 0.600000000000 1378780 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": 921106, "vin": [ { "gen": { "height": 921096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2328b1bf777e480e9660f57969aa1c268ebec3dd1083c90639be18db5bf156a" } } ], "extra": [ 1, 103, 57, 115, 93, 153, 89, 35, 105, 91, 96, 191, 42, 246, 200, 232, 99, 139, 186, 25, 239, 223, 131, 231, 63, 154, 105, 220, 58, 168, 223, 77, 29, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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