Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a768db8ac9f60bc184d716d6740dc08a016eaca1a19ba85b64f4bbde3bea694d

Tx prefix hash: 2e37914653328c8eba46b22a0a48ca7807c32e47c8b4c68ad839fe318f305f90
Tx public key: 184f5287350ed43429e2e31a63b5172aee0acbb5f1cd5676e413cdd716a53287
Timestamp: 1765458363 Timestamp [UCT]: 2025-12-11 13:06:03 Age [y:d:h:m:s]: 00:023:15:54:48
Block: 1431291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16954 RingCT/type: yes/0
Extra: 01184f5287350ed43429e2e31a63b5172aee0acbb5f1cd5676e413cdd716a53287021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46748d6e0939dc534092a0c0aef6aee84921a2d14ba89f5356381a6c0ca0674d 0.600000000000 1920048 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": 1431301, "vin": [ { "gen": { "height": 1431291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46748d6e0939dc534092a0c0aef6aee84921a2d14ba89f5356381a6c0ca0674d" } } ], "extra": [ 1, 24, 79, 82, 135, 53, 14, 212, 52, 41, 226, 227, 26, 99, 181, 23, 42, 238, 10, 203, 181, 241, 205, 86, 118, 228, 19, 205, 215, 22, 165, 50, 135, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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