Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e71b9ef0e37f8904a291e29f42676dc5afffe5338cddc1c05c2b2997d69dfca3

Tx prefix hash: 3ad631e45cf25dd8e796ac012e9120604ceebe6eafe0406d7541b0e310f6c4b8
Tx public key: 7aa28ab004e5e85fb92e02f86d494f6fc5f450d01cfd83f22290a18958631ba6
Timestamp: 1713663871 Timestamp [UCT]: 2024-04-21 01:44:31 Age [y:d:h:m:s]: 00:251:00:20:39
Block: 1005016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179676 RingCT/type: yes/0
Extra: 017aa28ab004e5e85fb92e02f86d494f6fc5f450d01cfd83f22290a18958631ba60211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 337814582e0dba035d3fab748e925de753538c3227cb8dc9cf0bd750ec0e4211 0.600000000000 1465594 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": 1005026, "vin": [ { "gen": { "height": 1005016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "337814582e0dba035d3fab748e925de753538c3227cb8dc9cf0bd750ec0e4211" } } ], "extra": [ 1, 122, 162, 138, 176, 4, 229, 232, 95, 185, 46, 2, 248, 109, 73, 79, 111, 197, 244, 80, 208, 28, 253, 131, 242, 34, 144, 161, 137, 88, 99, 27, 166, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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