Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07f1f1f13ba16b0765540e7aef8a2227cf22a3c19f3de281e8bf7b09186909a9

Tx prefix hash: dc76fdfa9affe1606fbe997075f3e68d70c7d9643970f40d1d39deff78b09ef0
Tx public key: 370e8112b440750dcd4a4262a5249a9165f819f243516cf1c5622ad8d0453bae
Timestamp: 1761550507 Timestamp [UCT]: 2025-10-27 07:35:07 Age [y:d:h:m:s]: 00:090:18:32:26
Block: 1398923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64793 RingCT/type: yes/0
Extra: 01370e8112b440750dcd4a4262a5249a9165f819f243516cf1c5622ad8d0453bae021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd2cd5fb5613d40adf2d271a24a66f0a6f69e89379909bed2cf719fd2a9b2485 0.600000000000 1887226 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": 1398933, "vin": [ { "gen": { "height": 1398923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd2cd5fb5613d40adf2d271a24a66f0a6f69e89379909bed2cf719fd2a9b2485" } } ], "extra": [ 1, 55, 14, 129, 18, 180, 64, 117, 13, 205, 74, 66, 98, 165, 36, 154, 145, 101, 248, 25, 242, 67, 81, 108, 241, 197, 98, 42, 216, 208, 69, 59, 174, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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