Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69960ed90a4a3c3d79345fb2250dfe08e715d5ff214487e0f14ebe2cd61bb905

Tx prefix hash: 7338d4a1577cad620211f04270d46aa81aaf78af5c51515c333f0eb21b5808ca
Tx public key: 31c4a94acdc6b6955d5a36d9123cc7c9a2462f867f1aab409c70c8f8e4782cd6
Timestamp: 1762441408 Timestamp [UCT]: 2025-11-06 15:03:28 Age [y:d:h:m:s]: 00:065:04:54:31
Block: 1406282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46709 RingCT/type: yes/0
Extra: 0131c4a94acdc6b6955d5a36d9123cc7c9a2462f867f1aab409c70c8f8e4782cd6021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0c145338d9fed61be26d9ff8bb9c4263455b7a84485688078ec581e94ac4b3d 0.600000000000 1894665 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": 1406292, "vin": [ { "gen": { "height": 1406282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0c145338d9fed61be26d9ff8bb9c4263455b7a84485688078ec581e94ac4b3d" } } ], "extra": [ 1, 49, 196, 169, 74, 205, 198, 182, 149, 93, 90, 54, 217, 18, 60, 199, 201, 162, 70, 47, 134, 127, 26, 171, 64, 156, 112, 200, 248, 228, 120, 44, 214, 2, 17, 0, 0, 0, 2, 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