Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e09ab361013c52c430e4f236842acdbe9f896fde24961a6983b525c3307cd82

Tx prefix hash: 2d056e498f127509948d48ed8cde406a70c0c4ce51d9adb45556c2bfbe763e44
Tx public key: 60143746feee4fd6c72173e4916fb666ce46c1c00db0afc366aa947a10bea083
Timestamp: 1676979263 Timestamp [UCT]: 2023-02-21 11:34:23 Age [y:d:h:m:s]: 01:271:21:48:06
Block: 701772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455245 RingCT/type: yes/0
Extra: 0160143746feee4fd6c72173e4916fb666ce46c1c00db0afc366aa947a10bea08302110000000574b6d784000000000000000000

1 output(s) for total of 2.902270953000 dcy

stealth address amount amount idx
00: 576c397a1f04b9a2f400aba7caf44ad4897b84d3d67c1e8545e666175d1ab2ee 2.902270953000 1145263 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": 701782, "vin": [ { "gen": { "height": 701772 } } ], "vout": [ { "amount": 2902270953, "target": { "key": "576c397a1f04b9a2f400aba7caf44ad4897b84d3d67c1e8545e666175d1ab2ee" } } ], "extra": [ 1, 96, 20, 55, 70, 254, 238, 79, 214, 199, 33, 115, 228, 145, 111, 182, 102, 206, 70, 193, 192, 13, 176, 175, 195, 102, 170, 148, 122, 16, 190, 160, 131, 2, 17, 0, 0, 0, 5, 116, 182, 215, 132, 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