Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfdf7ce79667298b34a1ab982acc9fc8cfe0d256fc456027d5b9ea342486c698

Tx prefix hash: 9ba688bf3fd42417518872958938f4fa87164f70f1e2eafaa0ae163da14f22d9
Tx public key: 05c22d30a1e5cc37a142ed7a1eac7080259c0e884676a9cd622b5ef0b6f93b98
Timestamp: 1704232903 Timestamp [UCT]: 2024-01-02 22:01:43 Age [y:d:h:m:s]: 01:313:10:09:08
Block: 926831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482834 RingCT/type: yes/0
Extra: 0105c22d30a1e5cc37a142ed7a1eac7080259c0e884676a9cd622b5ef0b6f93b9802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcbef0340e0998d0e1d037f3e0a0d157280524eff761d85c64497daf811629f8 0.600000000000 1384629 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": 926841, "vin": [ { "gen": { "height": 926831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcbef0340e0998d0e1d037f3e0a0d157280524eff761d85c64497daf811629f8" } } ], "extra": [ 1, 5, 194, 45, 48, 161, 229, 204, 55, 161, 66, 237, 122, 30, 172, 112, 128, 37, 156, 14, 136, 70, 118, 169, 205, 98, 43, 94, 240, 182, 249, 59, 152, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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