Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 069651c458786fee063e325be7304fa3d8427bcd281c86e97219663840db7280

Tx prefix hash: a0634712f9e0a3c6bce7d2b94642ec3adce8f6408440d3d8838d6aa48b17341e
Tx public key: a6a645c56a1631de752f8dcb6b268c45f0c0abb1fb69bda0e63743a2ff675449
Timestamp: 1747992633 Timestamp [UCT]: 2025-05-23 09:30:33 Age [y:d:h:m:s]: 00:254:23:42:50
Block: 1289100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179846 RingCT/type: yes/0
Extra: 01a6a645c56a1631de752f8dcb6b268c45f0c0abb1fb69bda0e63743a2ff6754490211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b50e7cf97ceb510fc018cfc2716997577a4cdfebf6eb6a27e3264d9e9d3550fb 0.600000000000 1776567 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": 1289110, "vin": [ { "gen": { "height": 1289100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b50e7cf97ceb510fc018cfc2716997577a4cdfebf6eb6a27e3264d9e9d3550fb" } } ], "extra": [ 1, 166, 166, 69, 197, 106, 22, 49, 222, 117, 47, 141, 203, 107, 38, 140, 69, 240, 192, 171, 177, 251, 105, 189, 160, 230, 55, 67, 162, 255, 103, 84, 73, 2, 17, 0, 0, 0, 2, 31, 144, 81, 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