Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f931f4f0d3f2e09e8e2af0842057889e5cb4724b5451f0d8da97aec7a2f9f035

Tx prefix hash: a59629a9e48b10a1f3488d5fda0b59d97753b6131bd111361fd8b905ed697e18
Tx public key: 0df5b0c1dce5b4c0373078d228aa0685258912fa5d02dca5fa235c3c24c86cb3
Timestamp: 1718450871 Timestamp [UCT]: 2024-06-15 11:27:51 Age [y:d:h:m:s]: 00:297:11:03:19
Block: 1044721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212554 RingCT/type: yes/0
Extra: 010df5b0c1dce5b4c0373078d228aa0685258912fa5d02dca5fa235c3c24c86cb30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a0f85dc3498c31a5012fccc80f03053726db44d864aa336e79f958e2212905b 0.600000000000 1514106 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": 1044731, "vin": [ { "gen": { "height": 1044721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a0f85dc3498c31a5012fccc80f03053726db44d864aa336e79f958e2212905b" } } ], "extra": [ 1, 13, 245, 176, 193, 220, 229, 180, 192, 55, 48, 120, 210, 40, 170, 6, 133, 37, 137, 18, 250, 93, 2, 220, 165, 250, 35, 92, 60, 36, 200, 108, 179, 2, 17, 0, 0, 0, 1, 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