Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 543ffe93a9c4dd8e6a281b7e208196ac09410e705970dca3e14fdce474ac2cf2

Tx prefix hash: 4e57de237d5e7dab78a4476f0a9c60527fb8c0468fcae369c0963b719cedfd12
Tx public key: 81b3fe49e5bccbb8fddc107cb2b475ecc11bcc759763860250b5152bf6595c94
Timestamp: 1712698500 Timestamp [UCT]: 2024-04-09 21:35:00 Age [y:d:h:m:s]: 01:036:03:18:56
Block: 997001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286816 RingCT/type: yes/0
Extra: 0181b3fe49e5bccbb8fddc107cb2b475ecc11bcc759763860250b5152bf6595c94021100000002bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c10d8c12b1eabd04f7d7a21d53db14d260e4533e5e43c9677cfa5f4556d8878 0.600000000000 1457429 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": 997011, "vin": [ { "gen": { "height": 997001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c10d8c12b1eabd04f7d7a21d53db14d260e4533e5e43c9677cfa5f4556d8878" } } ], "extra": [ 1, 129, 179, 254, 73, 229, 188, 203, 184, 253, 220, 16, 124, 178, 180, 117, 236, 193, 27, 204, 117, 151, 99, 134, 2, 80, 181, 21, 43, 246, 89, 92, 148, 2, 17, 0, 0, 0, 2, 191, 162, 34, 33, 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