Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24703b5cc5dab931459bb8e3dbb592fe960ec4aa69dfd8f1d79e4a5d8725a034

Tx prefix hash: d8fdc30fa7825bd49dd80d7010b0f3d2cc2a730b5e8d18815e6a14895154f27c
Tx public key: 114d263d233c56a9406b1515351256b3d2d4a4348cdb8c08a241c2cc1eb24f53
Timestamp: 1703745995 Timestamp [UCT]: 2023-12-28 06:46:35 Age [y:d:h:m:s]: 01:314:15:28:59
Block: 922800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483705 RingCT/type: yes/0
Extra: 01114d263d233c56a9406b1515351256b3d2d4a4348cdb8c08a241c2cc1eb24f5302110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02e3ba921f131d1730b27f9ffff9802beaff8ecb25bd68283a0cf2f6f20240f7 0.600000000000 1380504 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": 922810, "vin": [ { "gen": { "height": 922800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02e3ba921f131d1730b27f9ffff9802beaff8ecb25bd68283a0cf2f6f20240f7" } } ], "extra": [ 1, 17, 77, 38, 61, 35, 60, 86, 169, 64, 107, 21, 21, 53, 18, 86, 179, 210, 212, 164, 52, 140, 219, 140, 8, 162, 65, 194, 204, 30, 178, 79, 83, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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