Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d1fed5419694584fde2b1bdf89016ce0a5e54e2f9e622c5966547d345bb9b57

Tx prefix hash: c43883ac5c0bb978aeb659ba23ce63656782c4d9b63c05b8af50cbe9d017abb7
Tx public key: 2c763511a0f4b3709d27aad95c60b86db9f0f0439c917094940c7b0bdb2a4f42
Timestamp: 1707077449 Timestamp [UCT]: 2024-02-04 20:10:49 Age [y:d:h:m:s]: 01:073:18:31:49
Block: 950412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313796 RingCT/type: yes/0
Extra: 012c763511a0f4b3709d27aad95c60b86db9f0f0439c917094940c7b0bdb2a4f4202110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6059bcea27f3991dd44d958ac494ce807f4d738a1fe12fdc8749654a4fdbc218 0.600000000000 1409030 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": 950422, "vin": [ { "gen": { "height": 950412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6059bcea27f3991dd44d958ac494ce807f4d738a1fe12fdc8749654a4fdbc218" } } ], "extra": [ 1, 44, 118, 53, 17, 160, 244, 179, 112, 157, 39, 170, 217, 92, 96, 184, 109, 185, 240, 240, 67, 156, 145, 112, 148, 148, 12, 123, 11, 219, 42, 79, 66, 2, 17, 0, 0, 0, 9, 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