Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86fdfe0d20264b1fe6642bb7c63cc830ac3aa098c467c39050fd5c0c921f099c

Tx prefix hash: bb20fa552c3a60df4b2a06ee41d91f3b63ba458671a8247394f7b68a7e8d8833
Tx public key: 4b1a488db171d526f804e5aab4aa3274cf4d918f89824c884ada9309b97358b4
Timestamp: 1688798522 Timestamp [UCT]: 2023-07-08 06:42:02 Age [y:d:h:m:s]: 01:236:02:38:47
Block: 799147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429831 RingCT/type: yes/0
Extra: 014b1a488db171d526f804e5aab4aa3274cf4d918f89824c884ada9309b97358b4021100000004faf35c9c000000000000000000

1 output(s) for total of 1.380684275000 dcy

stealth address amount amount idx
00: de16300628eb354e738b75ad39ae478c094825f15431f1bf0ef4a6c943a0ce41 1.380684275000 1250130 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": 799157, "vin": [ { "gen": { "height": 799147 } } ], "vout": [ { "amount": 1380684275, "target": { "key": "de16300628eb354e738b75ad39ae478c094825f15431f1bf0ef4a6c943a0ce41" } } ], "extra": [ 1, 75, 26, 72, 141, 177, 113, 213, 38, 248, 4, 229, 170, 180, 170, 50, 116, 207, 77, 145, 143, 137, 130, 76, 136, 74, 218, 147, 9, 185, 115, 88, 180, 2, 17, 0, 0, 0, 4, 250, 243, 92, 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