Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 042a3a84fb0e973318bcdb62e50e576c8e9946e83c77074726394bd0d0c02834

Tx prefix hash: f0d249a80dfdbe454b8c1c97bbf2d81b7d2682be625e15b80be7e3dfb7c1505b
Tx public key: b2f67582f7697355d9753c6828b9534ce3670e5e4df1480074351db9c32ada3c
Timestamp: 1724887826 Timestamp [UCT]: 2024-08-28 23:30:26 Age [y:d:h:m:s]: 00:134:20:24:27
Block: 1098076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96456 RingCT/type: yes/0
Extra: 01b2f67582f7697355d9753c6828b9534ce3670e5e4df1480074351db9c32ada3c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6f4050f88c3c80819f526cbdfe96eeec9d76565bb5add698c9caf12da1ffd82 0.600000000000 1573667 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": 1098086, "vin": [ { "gen": { "height": 1098076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6f4050f88c3c80819f526cbdfe96eeec9d76565bb5add698c9caf12da1ffd82" } } ], "extra": [ 1, 178, 246, 117, 130, 247, 105, 115, 85, 217, 117, 60, 104, 40, 185, 83, 76, 227, 103, 14, 94, 77, 241, 72, 0, 116, 53, 29, 185, 195, 42, 218, 60, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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