Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7028495d12539f47aea44ef9e6ea0741368711d8901885afe42686e4c582fd1

Tx prefix hash: 85f6150b8b2c102efde5ba43bf9c4b29d5097d883b745a41b18dc5194c3bc9fc
Tx public key: 1002d27b3cbf0a63bc028cae3fe6774d2d3ba0c7d94bc329bed12e58e4c95958
Timestamp: 1721521099 Timestamp [UCT]: 2024-07-21 00:18:19 Age [y:d:h:m:s]: 00:328:18:58:35
Block: 1070160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234877 RingCT/type: yes/0
Extra: 011002d27b3cbf0a63bc028cae3fe6774d2d3ba0c7d94bc329bed12e58e4c959580211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 401e883af9567614a9d8e4a864738a400fa90bd6390e22b62676c91f9cbe6265 0.600000000000 1541879 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": 1070170, "vin": [ { "gen": { "height": 1070160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "401e883af9567614a9d8e4a864738a400fa90bd6390e22b62676c91f9cbe6265" } } ], "extra": [ 1, 16, 2, 210, 123, 60, 191, 10, 99, 188, 2, 140, 174, 63, 230, 119, 77, 45, 59, 160, 199, 217, 75, 195, 41, 190, 209, 46, 88, 228, 201, 89, 88, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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