Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f357cb0a001198d755596f1815cb4948cf5306845591a9061adf1f3637829a4

Tx prefix hash: 18fdc3e074e0581988541278c7109608c3c68bf50d92ac2dc18e79aa5d55c506
Tx public key: 2d30c7d57526660bb612bd0dd2184000ce54e5b929e3480d208caf7f753b0857
Timestamp: 1703989378 Timestamp [UCT]: 2023-12-31 02:22:58 Age [y:d:h:m:s]: 01:142:20:18:51
Block: 924811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363245 RingCT/type: yes/0
Extra: 012d30c7d57526660bb612bd0dd2184000ce54e5b929e3480d208caf7f753b0857021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56c6ef18f334561495c7229a2b1b2fc293cb21cba451834a3baeadb391d9a7d0 0.600000000000 1382569 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": 924821, "vin": [ { "gen": { "height": 924811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56c6ef18f334561495c7229a2b1b2fc293cb21cba451834a3baeadb391d9a7d0" } } ], "extra": [ 1, 45, 48, 199, 213, 117, 38, 102, 11, 182, 18, 189, 13, 210, 24, 64, 0, 206, 84, 229, 185, 41, 227, 72, 13, 32, 140, 175, 127, 117, 59, 8, 87, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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