Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e09d610bc130c065f9d8e70938a347cffac165636246a0b5cf4c4c1590327a8a

Tx prefix hash: 79a3aee3da682cf59000614266bf35e549b44c436aaf904b0a4f09f0220f95fd
Tx public key: b1afb119dd1d89aa80f8bb59b2b687271a29b28192864e2b5adbde31d1ba0b46
Timestamp: 1723282892 Timestamp [UCT]: 2024-08-10 09:41:32 Age [y:d:h:m:s]: 00:219:02:32:37
Block: 1084781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156483 RingCT/type: yes/0
Extra: 01b1afb119dd1d89aa80f8bb59b2b687271a29b28192864e2b5adbde31d1ba0b4602110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2d8b88d1cc0c80e5d7f4dba61c54fbbe413d067878140696ab9e563c489ede3 0.600000000000 1559176 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": 1084791, "vin": [ { "gen": { "height": 1084781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2d8b88d1cc0c80e5d7f4dba61c54fbbe413d067878140696ab9e563c489ede3" } } ], "extra": [ 1, 177, 175, 177, 25, 221, 29, 137, 170, 128, 248, 187, 89, 178, 182, 135, 39, 26, 41, 178, 129, 146, 134, 78, 43, 90, 219, 222, 49, 209, 186, 11, 70, 2, 17, 0, 0, 0, 10, 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