Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b26ab6b87313389e456120efb10f13c87b807ed16100dcb13e489d9643b82107

Tx prefix hash: 92a75647ac6a80fdf73d6f5395e747cfda80790deec7496aebad8df83440e091
Tx public key: 22d6fa567e16a94f44960c5e2b82c5813f4c05e303cc91a3a1dc87bca226a96e
Timestamp: 1730738908 Timestamp [UCT]: 2024-11-04 16:48:28 Age [y:d:h:m:s]: 00:019:14:56:12
Block: 1146499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14048 RingCT/type: yes/0
Extra: 0122d6fa567e16a94f44960c5e2b82c5813f4c05e303cc91a3a1dc87bca226a96e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bf9096ad78622bb8c3dca24f196ed7b0d5a2868fca6b7b14641163915d2cc3d 0.600000000000 1631152 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": 1146509, "vin": [ { "gen": { "height": 1146499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bf9096ad78622bb8c3dca24f196ed7b0d5a2868fca6b7b14641163915d2cc3d" } } ], "extra": [ 1, 34, 214, 250, 86, 126, 22, 169, 79, 68, 150, 12, 94, 43, 130, 197, 129, 63, 76, 5, 227, 3, 204, 145, 163, 161, 220, 135, 188, 162, 38, 169, 110, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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