Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1a8d2b185a28c273a99646269cfd1e32829c0f01e7957f2fadbd23500d75b18

Tx prefix hash: 65529d08718148d4e695794443e1acb0e945bd061196c04598b18c867bcdc6f6
Tx public key: 65e19213b90eb3352e115ace5b84aaae1b57b4d678ac9b9d7a2523cf22ffe56f
Timestamp: 1722836320 Timestamp [UCT]: 2024-08-05 05:38:40 Age [y:d:h:m:s]: 01:100:14:10:02
Block: 1081061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330377 RingCT/type: yes/0
Extra: 0165e19213b90eb3352e115ace5b84aaae1b57b4d678ac9b9d7a2523cf22ffe56f021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e9cd120d1223fb1e0d8f0cd0a1a45fc804c9ab3fd10116154d2a9bb05746e78 0.600000000000 1554662 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": 1081071, "vin": [ { "gen": { "height": 1081061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e9cd120d1223fb1e0d8f0cd0a1a45fc804c9ab3fd10116154d2a9bb05746e78" } } ], "extra": [ 1, 101, 225, 146, 19, 185, 14, 179, 53, 46, 17, 90, 206, 91, 132, 170, 174, 27, 87, 180, 214, 120, 172, 155, 157, 122, 37, 35, 207, 34, 255, 229, 111, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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