Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 437505db40bbfbb3b6cb443a2332c64d0048b7f7c3c0a8c89a32b2832f6659a3

Tx prefix hash: 0e09153e43f8cfed5092dca64efb90f63eea7566ab2fea2d6658da83df42d53b
Tx public key: 2dc158a8d984889db79d9d519c147c373fe641d48af4a41d2328174c11dec8da
Timestamp: 1709190416 Timestamp [UCT]: 2024-02-29 07:06:56 Age [y:d:h:m:s]: 01:252:14:40:24
Block: 967945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439268 RingCT/type: yes/0
Extra: 012dc158a8d984889db79d9d519c147c373fe641d48af4a41d2328174c11dec8da02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e198f46463f21d08431cbc1e6b3465a7c332715296186e8d4779244c3c49913 0.600000000000 1427740 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": 967955, "vin": [ { "gen": { "height": 967945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e198f46463f21d08431cbc1e6b3465a7c332715296186e8d4779244c3c49913" } } ], "extra": [ 1, 45, 193, 88, 168, 217, 132, 136, 157, 183, 157, 157, 81, 156, 20, 124, 55, 63, 230, 65, 212, 138, 244, 164, 29, 35, 40, 23, 76, 17, 222, 200, 218, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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