Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dea1d347d3c5b5de4e4b331b178a0772b57fd7269f43ff62694e5202c5b45a1c

Tx prefix hash: 35e9a2ed5aef1d27657e5e0c45f99e329875a5f7bd3b6b298382edfe8cd9099e
Tx public key: 8ebd523cd9cc56bf35aa62c19b69dd77b4be8b13af5503c1e64d467628fefcfc
Timestamp: 1638659051 Timestamp [UCT]: 2021-12-04 23:04:11 Age [y:d:h:m:s]: 02:360:13:20:50
Block: 388544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 775723 RingCT/type: yes/0
Extra: 018ebd523cd9cc56bf35aa62c19b69dd77b4be8b13af5503c1e64d467628fefcfc021100000012b494d89c000000000000000000

1 output(s) for total of 31.667770579000 dcy

stealth address amount amount idx
00: e51bc7c3fca4a678757065af64d43b580f137fab4d52615d4b2f2ea9b63c23b2 31.667770579000 783237 of 0

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": 388554, "vin": [ { "gen": { "height": 388544 } } ], "vout": [ { "amount": 31667770579, "target": { "key": "e51bc7c3fca4a678757065af64d43b580f137fab4d52615d4b2f2ea9b63c23b2" } } ], "extra": [ 1, 142, 189, 82, 60, 217, 204, 86, 191, 53, 170, 98, 193, 155, 105, 221, 119, 180, 190, 139, 19, 175, 85, 3, 193, 230, 77, 70, 118, 40, 254, 252, 252, 2, 17, 0, 0, 0, 18, 180, 148, 216, 156, 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