Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae4ded5e7e63e9ba206fef88e9902d8b7ca869d5884bf6039d8c28286a294f86

Tx prefix hash: 768f19300e576d812ca588759741180b8a71b39b1255c886a06c6ce2586ac304
Tx public key: 1cd243f6ada19cba107e699d73f09c86675d095f8335ee1df76a1b126997f2e5
Timestamp: 1736219119 Timestamp [UCT]: 2025-01-07 03:05:19 Age [y:d:h:m:s]: 00:161:11:16:28
Block: 1191881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115127 RingCT/type: yes/0
Extra: 011cd243f6ada19cba107e699d73f09c86675d095f8335ee1df76a1b126997f2e50211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f35d7da2a82416f814ae9485eb68e60fb91b0ca8b4528d8b61e181e675a6a038 0.600000000000 1678424 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": 1191891, "vin": [ { "gen": { "height": 1191881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f35d7da2a82416f814ae9485eb68e60fb91b0ca8b4528d8b61e181e675a6a038" } } ], "extra": [ 1, 28, 210, 67, 246, 173, 161, 156, 186, 16, 126, 105, 157, 115, 240, 156, 134, 103, 93, 9, 95, 131, 53, 238, 29, 247, 106, 27, 18, 105, 151, 242, 229, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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