Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00f00e0e353c65fd704ff18a7862a9c78cd73b523daaca32d4f5e68766623fd1

Tx prefix hash: 28db63b56e0061f9cd7b07d1745c1ea065549add8b7f633bc6093a4df938ac86
Tx public key: 8597b9d05522158c9bde1b94a755163bef6db9b1a1276e60d03c7083ca1def2a
Timestamp: 1735685555 Timestamp [UCT]: 2024-12-31 22:52:35 Age [y:d:h:m:s]: 00:103:20:51:45
Block: 1187464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74031 RingCT/type: yes/0
Extra: 018597b9d05522158c9bde1b94a755163bef6db9b1a1276e60d03c7083ca1def2a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c36b0e1ee900fec40bae794a77994261d18321e4b9b00bb885b9504edbb051a7 0.600000000000 1673955 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": 1187474, "vin": [ { "gen": { "height": 1187464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c36b0e1ee900fec40bae794a77994261d18321e4b9b00bb885b9504edbb051a7" } } ], "extra": [ 1, 133, 151, 185, 208, 85, 34, 21, 140, 155, 222, 27, 148, 167, 85, 22, 59, 239, 109, 185, 177, 161, 39, 110, 96, 208, 60, 112, 131, 202, 29, 239, 42, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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