Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00e68a2ca3ee345f5a948a1951db7f85c29d45d7f8157c26e74313373544099b

Tx prefix hash: 233cded6f7bfe251f0f5a9dd853ba7d1424c7761858d862c7017ce5df409f068
Tx public key: 1e571e42273b8c5d930318bd2223cd528b373f1dc44f5515448418a0026f0e48
Timestamp: 1719567914 Timestamp [UCT]: 2024-06-28 09:45:14 Age [y:d:h:m:s]: 00:284:09:40:32
Block: 1053971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203210 RingCT/type: yes/0
Extra: 011e571e42273b8c5d930318bd2223cd528b373f1dc44f5515448418a0026f0e480211000000050cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a8cc496a6c63341edb529e3e976696dc118579d04d99ebd87c8c64c7c862370 0.600000000000 1524330 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": 1053981, "vin": [ { "gen": { "height": 1053971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a8cc496a6c63341edb529e3e976696dc118579d04d99ebd87c8c64c7c862370" } } ], "extra": [ 1, 30, 87, 30, 66, 39, 59, 140, 93, 147, 3, 24, 189, 34, 35, 205, 82, 139, 55, 63, 29, 196, 79, 85, 21, 68, 132, 24, 160, 2, 111, 14, 72, 2, 17, 0, 0, 0, 5, 12, 206, 6, 54, 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