Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18b0b9b727184318f9b9c04cc88e0c1f403f399a7204a5c0532d210464c6c2b7

Tx prefix hash: a2f1b4e730430398302666759764c452717a47b179394f5e691dbbdd1843979f
Tx public key: 2791e85d85bf6f505467f0baa4456fa836adeb6f4ccdac8e78862c465eb717e0
Timestamp: 1712482331 Timestamp [UCT]: 2024-04-07 09:32:11 Age [y:d:h:m:s]: 00:324:02:36:46
Block: 995208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231714 RingCT/type: yes/0
Extra: 012791e85d85bf6f505467f0baa4456fa836adeb6f4ccdac8e78862c465eb717e002110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5885d76d826c850ab85ccea26374a2dcbf9a6a4f3fd5ba04a99acc49365de01 0.600000000000 1455614 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": 995218, "vin": [ { "gen": { "height": 995208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5885d76d826c850ab85ccea26374a2dcbf9a6a4f3fd5ba04a99acc49365de01" } } ], "extra": [ 1, 39, 145, 232, 93, 133, 191, 111, 80, 84, 103, 240, 186, 164, 69, 111, 168, 54, 173, 235, 111, 76, 205, 172, 142, 120, 134, 44, 70, 94, 183, 23, 224, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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