Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28f6ef67fc491df0891e4843091c6a42a909dfdf6a20f04b1c8bb165a33bd857

Tx prefix hash: a4fcab564871336b66adc7b43e6fe518eeeaf54807a2441834f064d2fc4403a4
Tx public key: 7c399ced1b29de653e003790f7c611a8dcdfbebd0dd6e8d982ad0e944f1e2053
Timestamp: 1708074258 Timestamp [UCT]: 2024-02-16 09:04:18 Age [y:d:h:m:s]: 01:044:09:27:24
Block: 958676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292767 RingCT/type: yes/0
Extra: 017c399ced1b29de653e003790f7c611a8dcdfbebd0dd6e8d982ad0e944f1e205302110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d17cf23265f72412ab9dee5203381b54c6210fe1a931a6f10513bfda5c90415 0.600000000000 1418037 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": 958686, "vin": [ { "gen": { "height": 958676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d17cf23265f72412ab9dee5203381b54c6210fe1a931a6f10513bfda5c90415" } } ], "extra": [ 1, 124, 57, 156, 237, 27, 41, 222, 101, 62, 0, 55, 144, 247, 198, 17, 168, 220, 223, 190, 189, 13, 214, 232, 217, 130, 173, 14, 148, 79, 30, 32, 83, 2, 17, 0, 0, 0, 11, 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