Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70ecf91ec0c2c3557dd87f255edf89288fc428412fdcc1fd32b051a8e4e6aac4

Tx prefix hash: 782c63f72edaf181a3cede6c0b73cd8748c057bbac0b8acb84e20847864f30e4
Tx public key: a9e177053cd98756af80ffee79069090f8a497acc4b1c8291277df05cb1f1e82
Timestamp: 1761840378 Timestamp [UCT]: 2025-10-30 16:06:18 Age [y:d:h:m:s]: 00:051:18:04:40
Block: 1401313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37049 RingCT/type: yes/0
Extra: 01a9e177053cd98756af80ffee79069090f8a497acc4b1c8291277df05cb1f1e82021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b889aaa5c49e957e00c35e0b32370238d5db2a24c4b2b6c2d5fafb8730e54049 0.600000000000 1889632 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": 1401323, "vin": [ { "gen": { "height": 1401313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b889aaa5c49e957e00c35e0b32370238d5db2a24c4b2b6c2d5fafb8730e54049" } } ], "extra": [ 1, 169, 225, 119, 5, 60, 217, 135, 86, 175, 128, 255, 238, 121, 6, 144, 144, 248, 164, 151, 172, 196, 177, 200, 41, 18, 119, 223, 5, 203, 31, 30, 130, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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