Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb64a8c65a1602a0973ed073d6e518130830cd2f4681388da328999509bf5ed9

Tx prefix hash: ffb98388cec48b84de79537dc74412bcc4cf49da353317ccd9486120d80b6aae
Tx public key: 8304085397a32a04db16a1dbd1d60d2e14730e6cd7d01d7a95c4ddcc65b30d88
Timestamp: 1696737698 Timestamp [UCT]: 2023-10-08 04:01:38 Age [y:d:h:m:s]: 02:034:16:46:15
Block: 864907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544418 RingCT/type: yes/0
Extra: 018304085397a32a04db16a1dbd1d60d2e14730e6cd7d01d7a95c4ddcc65b30d8802110000000133af99f4000000000000000000

1 output(s) for total of 0.835995816000 dcy

stealth address amount amount idx
00: c81c65aa54e88db16e229e03432ca2b5a061a1531c11b99f77ae90f879c0a41f 0.835995816000 1319431 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": 864917, "vin": [ { "gen": { "height": 864907 } } ], "vout": [ { "amount": 835995816, "target": { "key": "c81c65aa54e88db16e229e03432ca2b5a061a1531c11b99f77ae90f879c0a41f" } } ], "extra": [ 1, 131, 4, 8, 83, 151, 163, 42, 4, 219, 22, 161, 219, 209, 214, 13, 46, 20, 115, 14, 108, 215, 208, 29, 122, 149, 196, 221, 204, 101, 179, 13, 136, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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