Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9f19f144d4d9211400ec0ffd90ff2b604fd25ebbb8de212f8649e82494075b7

Tx prefix hash: a2e95df9c7660d3fed4a0afd3e045f28043d3c4c2c1def9cc129a090e2f82876
Tx public key: 1bf4db78830329ce47c3b550ce776677c844b47a51bb27b6c9ac6e310c61935c
Timestamp: 1733702600 Timestamp [UCT]: 2024-12-09 00:03:20 Age [y:d:h:m:s]: 00:099:15:44:30
Block: 1171072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71010 RingCT/type: yes/0
Extra: 011bf4db78830329ce47c3b550ce776677c844b47a51bb27b6c9ac6e310c61935c02110000000601491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e894a11d88e533ce8de70f8d63f35220639802c98d8e8e47b06e5cb541f8e165 0.600000000000 1656807 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": 1171082, "vin": [ { "gen": { "height": 1171072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e894a11d88e533ce8de70f8d63f35220639802c98d8e8e47b06e5cb541f8e165" } } ], "extra": [ 1, 27, 244, 219, 120, 131, 3, 41, 206, 71, 195, 181, 80, 206, 119, 102, 119, 200, 68, 180, 122, 81, 187, 39, 182, 201, 172, 110, 49, 12, 97, 147, 92, 2, 17, 0, 0, 0, 6, 1, 73, 31, 136, 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