Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 280fe5b4d3844f9eb20a25f3aed231d18f3f835134e353bf64230837891db55b

Tx prefix hash: 7f388bac6e9ae2faae6080b20b3453109f7d6cfa269ae41ed5a9a364980f9832
Tx public key: 7dc83cebc8fdd14e87182423b5ab34dc3c2818eccd2a72c8167776e6407c28a2
Timestamp: 1682003902 Timestamp [UCT]: 2023-04-20 15:18:22 Age [y:d:h:m:s]: 02:008:17:15:41
Block: 742794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528385 RingCT/type: yes/0
Extra: 017dc83cebc8fdd14e87182423b5ab34dc3c2818eccd2a72c8167776e6407c28a202110000000275e3f0e9000000000000000000

1 output(s) for total of 2.122341876000 dcy

stealth address amount amount idx
00: 0e2d9b291ff78f5237110fafbccf94db9d493922ebc65fde134dcb62b83c7567 2.122341876000 1189793 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": 742804, "vin": [ { "gen": { "height": 742794 } } ], "vout": [ { "amount": 2122341876, "target": { "key": "0e2d9b291ff78f5237110fafbccf94db9d493922ebc65fde134dcb62b83c7567" } } ], "extra": [ 1, 125, 200, 60, 235, 200, 253, 209, 78, 135, 24, 36, 35, 181, 171, 52, 220, 60, 40, 24, 236, 205, 42, 114, 200, 22, 119, 118, 230, 64, 124, 40, 162, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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