Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4699ab1e9b73c7b32ffc3bba59c710fc68be29300ab5cce66d6604a4bc7ab0a

Tx prefix hash: 30ea14bd33084a6f7c23ed1a35c85afd13864a50d5c3a2212f196deac85fefa2
Tx public key: b7e014af73288c314bf6677371881ca28cec06367c45d3920ae4dc2c7061bd40
Timestamp: 1699681657 Timestamp [UCT]: 2023-11-11 05:47:37 Age [y:d:h:m:s]: 01:127:06:22:40
Block: 889106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352158 RingCT/type: yes/0
Extra: 01b7e014af73288c314bf6677371881ca28cec06367c45d3920ae4dc2c7061bd40021100000003faf35c9c000000000000000000

1 output(s) for total of 0.695060704000 dcy

stealth address amount amount idx
00: 42bd74164b8f34d33ffc9fbf0d18c9bab73b15bb0adb6b6f31ba48b8d6f05e83 0.695060704000 1345083 of 0

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": 889116, "vin": [ { "gen": { "height": 889106 } } ], "vout": [ { "amount": 695060704, "target": { "key": "42bd74164b8f34d33ffc9fbf0d18c9bab73b15bb0adb6b6f31ba48b8d6f05e83" } } ], "extra": [ 1, 183, 224, 20, 175, 115, 40, 140, 49, 75, 246, 103, 115, 113, 136, 28, 162, 140, 236, 6, 54, 124, 69, 211, 146, 10, 228, 220, 44, 112, 97, 189, 64, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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