Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfd3b263c828b054fc20c9308ce4324945f6975588a5f8c734c5114bf37e7829

Tx prefix hash: d2430ff2b868a8e86004b6d7b49f278784fec8f6469ddbe2c835ef7ca68277e7
Tx public key: e6fc8c017214b289fe4564d92326a5e7c5008bc2a5f4bce48b0e78daedd8d5c4
Timestamp: 1715421444 Timestamp [UCT]: 2024-05-11 09:57:24 Age [y:d:h:m:s]: 00:342:02:25:55
Block: 1019625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244515 RingCT/type: yes/0
Extra: 01e6fc8c017214b289fe4564d92326a5e7c5008bc2a5f4bce48b0e78daedd8d5c402110000000441ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 370d77a26e521d135026f244c15abbec98c158b3028fede6564182aceb20e504 0.600000000000 1483650 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": 1019635, "vin": [ { "gen": { "height": 1019625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "370d77a26e521d135026f244c15abbec98c158b3028fede6564182aceb20e504" } } ], "extra": [ 1, 230, 252, 140, 1, 114, 20, 178, 137, 254, 69, 100, 217, 35, 38, 165, 231, 197, 0, 139, 194, 165, 244, 188, 228, 139, 14, 120, 218, 237, 216, 213, 196, 2, 17, 0, 0, 0, 4, 65, 238, 28, 155, 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