Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08d2ab4dec634158f4b910e154c44734f9cd9fc59688f2019751d7cd0c55e179

Tx prefix hash: 6841e4fd1712e62b17f8db10f2157fa8852e04a5055540685a28880ece9a6735
Tx public key: 9a0f6642def22db801e3499542486e8c9d1dcaf64fdc5894174c4d6ccb8195b6
Timestamp: 1636717371 Timestamp [UCT]: 2021-11-12 11:42:51 Age [y:d:h:m:s]: 03:167:12:41:09
Block: 372779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 898158 RingCT/type: yes/0
Extra: 019a0f6642def22db801e3499542486e8c9d1dcaf64fdc5894174c4d6ccb8195b6021100000008f79c6ccf000000000000000000

1 output(s) for total of 35.713204061000 dcy

stealth address amount amount idx
00: 78e508239857282fea866c4e2bf030850f3ae5e75bb5605df2fa8cdbb92d569e 35.713204061000 755047 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": 372789, "vin": [ { "gen": { "height": 372779 } } ], "vout": [ { "amount": 35713204061, "target": { "key": "78e508239857282fea866c4e2bf030850f3ae5e75bb5605df2fa8cdbb92d569e" } } ], "extra": [ 1, 154, 15, 102, 66, 222, 242, 45, 184, 1, 227, 73, 149, 66, 72, 110, 140, 157, 29, 202, 246, 79, 220, 88, 148, 23, 76, 77, 108, 203, 129, 149, 182, 2, 17, 0, 0, 0, 8, 247, 156, 108, 207, 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