Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42f1582287a1f15fcd28c5b8f3282603515f20be0c9694f4e232c0407db79a39

Tx prefix hash: 84cd781051a7b194bd068cf881b9e707ec8453fce72f6d854c1d068e8bc39805
Tx public key: 4684943f89a4fd4dd8fc872f15e3f1dfc233e7571d113cd5cec99edc5f7bf447
Timestamp: 1749442607 Timestamp [UCT]: 2025-06-09 04:16:47 Age [y:d:h:m:s]: 00:154:17:21:56
Block: 1301110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108241 RingCT/type: yes/0
Extra: 014684943f89a4fd4dd8fc872f15e3f1dfc233e7571d113cd5cec99edc5f7bf447021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9caa594d3c080412ac3d56d3d19e184ac7e30563cc349bd8d3051bdc5abf1666 0.600000000000 1788663 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": 1301120, "vin": [ { "gen": { "height": 1301110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9caa594d3c080412ac3d56d3d19e184ac7e30563cc349bd8d3051bdc5abf1666" } } ], "extra": [ 1, 70, 132, 148, 63, 137, 164, 253, 77, 216, 252, 135, 47, 21, 227, 241, 223, 194, 51, 231, 87, 29, 17, 60, 213, 206, 201, 158, 220, 95, 123, 244, 71, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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