Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f01da03e83c178d9538198864e9771c775d65572a1ac4666f0ff6872305b4c35

Tx prefix hash: 4b929a4ce0545cdbd9a98a3a7f94c0e5ebc3440a24f31b94b7107e1f2881eb21
Tx public key: 8b0acbe0517b47f0eb05ff2155ea34930307fa3ce3b6ae1912d72a0eb3a0e803
Timestamp: 1759424776 Timestamp [UCT]: 2025-10-02 17:06:16 Age [y:d:h:m:s]: 00:040:14:27:52
Block: 1381285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29075 RingCT/type: yes/0
Extra: 018b0acbe0517b47f0eb05ff2155ea34930307fa3ce3b6ae1912d72a0eb3a0e80302110000000697baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6153717ef716eaa675b6e626e057f464d8b2720f136c04addeb498bee826b061 0.600000000000 1869404 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": 1381295, "vin": [ { "gen": { "height": 1381285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6153717ef716eaa675b6e626e057f464d8b2720f136c04addeb498bee826b061" } } ], "extra": [ 1, 139, 10, 203, 224, 81, 123, 71, 240, 235, 5, 255, 33, 85, 234, 52, 147, 3, 7, 250, 60, 227, 182, 174, 25, 18, 215, 42, 14, 179, 160, 232, 3, 2, 17, 0, 0, 0, 6, 151, 186, 249, 34, 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