Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 166f1ca2a58bdc100f86edfe0d3384b37fa30fb79d6597ef0fcd181a2cc8d003

Tx prefix hash: 47ca59d06260aa70629be500dc913d6209d6033fd8c98331fd2dc153c5bb2bc0
Tx public key: 657aaeef56ad2b851ccb87bb88d69dbc77b44e0574508d4d3cdec2579f40f9c3
Timestamp: 1760632297 Timestamp [UCT]: 2025-10-16 16:31:37 Age [y:d:h:m:s]: 00:048:10:16:24
Block: 1391303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34670 RingCT/type: yes/0
Extra: 01657aaeef56ad2b851ccb87bb88d69dbc77b44e0574508d4d3cdec2579f40f9c302110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3af6602ee89022af7b22b154273bd065b718070a8aebba317cfc80c5ba43fb0 0.600000000000 1879550 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": 1391313, "vin": [ { "gen": { "height": 1391303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3af6602ee89022af7b22b154273bd065b718070a8aebba317cfc80c5ba43fb0" } } ], "extra": [ 1, 101, 122, 174, 239, 86, 173, 43, 133, 28, 203, 135, 187, 136, 214, 157, 188, 119, 180, 78, 5, 116, 80, 141, 77, 60, 222, 194, 87, 159, 64, 249, 195, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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