Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f7c8dd420120d8cd8f952cbeafe3f3a855ad53241bad345bc4dd93d06130ded

Tx prefix hash: 70d7503973cd3780852e7ceae54e70446bf1815ebf014087bfff38accd7a2f08
Tx public key: a582d180ea363388a256fcfadf3fafd0f8c407b02ab50d4a3a6b7f4a90ea4982
Timestamp: 1718324568 Timestamp [UCT]: 2024-06-14 00:22:48 Age [y:d:h:m:s]: 00:167:10:41:36
Block: 1043672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119832 RingCT/type: yes/0
Extra: 01a582d180ea363388a256fcfadf3fafd0f8c407b02ab50d4a3a6b7f4a90ea49820211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e7b566a9752d354af0d52ff10cade932b087134ca3c74956b78e8e53cbe9faf 0.600000000000 1512829 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": 1043682, "vin": [ { "gen": { "height": 1043672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e7b566a9752d354af0d52ff10cade932b087134ca3c74956b78e8e53cbe9faf" } } ], "extra": [ 1, 165, 130, 209, 128, 234, 54, 51, 136, 162, 86, 252, 250, 223, 63, 175, 208, 248, 196, 7, 176, 42, 181, 13, 74, 58, 107, 127, 74, 144, 234, 73, 130, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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