Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ef67099547e91878550237ea44ae8d874c34ab0c1e024e79333b8b0baf43927

Tx prefix hash: 805c7a8724cfa23702ba7c5a815f1744ffa18054f3767a6c604c1afa1900d7d0
Tx public key: e34dcd96db3d3f1176b0a114d70a532bb20cda86b313cbf3cbf6455b7208d79c
Timestamp: 1729511782 Timestamp [UCT]: 2024-10-21 11:56:22 Age [y:d:h:m:s]: 00:034:02:08:24
Block: 1136371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24366 RingCT/type: yes/0
Extra: 01e34dcd96db3d3f1176b0a114d70a532bb20cda86b313cbf3cbf6455b7208d79c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d51c7a1f977ee4c24bb83038b694e75271ad3bca2579cf40a76183f8944f77e4 0.600000000000 1619716 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": 1136381, "vin": [ { "gen": { "height": 1136371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d51c7a1f977ee4c24bb83038b694e75271ad3bca2579cf40a76183f8944f77e4" } } ], "extra": [ 1, 227, 77, 205, 150, 219, 61, 63, 17, 118, 176, 161, 20, 215, 10, 83, 43, 178, 12, 218, 134, 179, 19, 203, 243, 203, 246, 69, 91, 114, 8, 215, 156, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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