Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2695f700ba13d47ebf5c1581b7fc5fbf4418a95a371d308fdb8ac3eafef8cfdc

Tx prefix hash: b98bea3bea5c2d373e429d04b3938152375cd2c4100e89b52e393d41807a8b43
Tx public key: b3885c856e38782d845cd5b79a798c2e303edbc8f626e003d3d4aa610a85a5fc
Timestamp: 1695562403 Timestamp [UCT]: 2023-09-24 13:33:23 Age [y:d:h:m:s]: 01:196:22:40:38
Block: 855156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401810 RingCT/type: yes/0
Extra: 01b3885c856e38782d845cd5b79a798c2e303edbc8f626e003d3d4aa610a85a5fc02110000000e4b8f5122000000000000000000

1 output(s) for total of 0.900561194000 dcy

stealth address amount amount idx
00: fff0c515eae1894a28b2aacc1f6f76708bff7400b7d80c9bfc3bbb49c956272a 0.900561194000 1309160 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": 855166, "vin": [ { "gen": { "height": 855156 } } ], "vout": [ { "amount": 900561194, "target": { "key": "fff0c515eae1894a28b2aacc1f6f76708bff7400b7d80c9bfc3bbb49c956272a" } } ], "extra": [ 1, 179, 136, 92, 133, 110, 56, 120, 45, 132, 92, 213, 183, 154, 121, 140, 46, 48, 62, 219, 200, 246, 38, 224, 3, 211, 212, 170, 97, 10, 133, 165, 252, 2, 17, 0, 0, 0, 14, 75, 143, 81, 34, 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