Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fab925b09cf43ffb6fbfc39434bbc6ffdebe226c31a4501199b9fe971da206b7

Tx prefix hash: d0e8c346e744136c7196b04df0bcd4213c080f936ed34e67190e6df9beffb7a3
Tx public key: 5fd1de4cf41a2e2a6bec54cf7ad6ee1e181caf9d317ffad4895d3f75dc829f2d
Timestamp: 1705197048 Timestamp [UCT]: 2024-01-14 01:50:48 Age [y:d:h:m:s]: 02:015:16:54:19
Block: 934814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530840 RingCT/type: yes/0
Extra: 015fd1de4cf41a2e2a6bec54cf7ad6ee1e181caf9d317ffad4895d3f75dc829f2d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3ec9a6761ffb34e64d492103376ff2b5aa3dcd5d4f2844b51c316289959acdd 0.600000000000 1392830 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": 934824, "vin": [ { "gen": { "height": 934814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3ec9a6761ffb34e64d492103376ff2b5aa3dcd5d4f2844b51c316289959acdd" } } ], "extra": [ 1, 95, 209, 222, 76, 244, 26, 46, 42, 107, 236, 84, 207, 122, 214, 238, 30, 24, 28, 175, 157, 49, 127, 250, 212, 137, 93, 63, 117, 220, 130, 159, 45, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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