Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 128da31786c063e0a8eeb7030a859e51c513b8d208566dbbf5707e4f4870d08d

Tx prefix hash: 389921eee4fc0625ba27fbbed5de6ec18d683d1fe383dc794621c0b6e2c767be
Tx public key: b8f5bf3c14875edc89e0b917f0b3e35a238d18ef236597ef5cf7ed3710534c8c
Timestamp: 1720524004 Timestamp [UCT]: 2024-07-09 11:20:04 Age [y:d:h:m:s]: 00:213:06:36:19
Block: 1061908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152330 RingCT/type: yes/0
Extra: 01b8f5bf3c14875edc89e0b917f0b3e35a238d18ef236597ef5cf7ed3710534c8c02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f74e5d21fa0e07527099f79832f8acfbd3eeea97462be022c993841ddc80a402 0.600000000000 1532407 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": 1061918, "vin": [ { "gen": { "height": 1061908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f74e5d21fa0e07527099f79832f8acfbd3eeea97462be022c993841ddc80a402" } } ], "extra": [ 1, 184, 245, 191, 60, 20, 135, 94, 220, 137, 224, 185, 23, 240, 179, 227, 90, 35, 141, 24, 239, 35, 101, 151, 239, 92, 247, 237, 55, 16, 83, 76, 140, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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