Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba401895382faf68764cc41fce9c10568dd57cb312ea90f24eeacbddea253243

Tx prefix hash: d829e3c7952fd4d0fba40bb23007e35d42f0a4afd8f9b4a9496d3bee2c90eafe
Tx public key: a6f097db536c2af5d5e941cf7469a8b0e5be1fc4a418cb13dab76ef0f71cbcc0
Timestamp: 1693540940 Timestamp [UCT]: 2023-09-01 04:02:20 Age [y:d:h:m:s]: 01:216:04:32:47
Block: 838366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415645 RingCT/type: yes/0
Extra: 01a6f097db536c2af5d5e941cf7469a8b0e5be1fc4a418cb13dab76ef0f71cbcc00211000000064b8f5122000000000000000000

1 output(s) for total of 1.023635864000 dcy

stealth address amount amount idx
00: 85ef29b6c41f6b89de0e884788611a7d574ba5c5fac9ac9b9962093733b1bd52 1.023635864000 1291096 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": 838376, "vin": [ { "gen": { "height": 838366 } } ], "vout": [ { "amount": 1023635864, "target": { "key": "85ef29b6c41f6b89de0e884788611a7d574ba5c5fac9ac9b9962093733b1bd52" } } ], "extra": [ 1, 166, 240, 151, 219, 83, 108, 42, 245, 213, 233, 65, 207, 116, 105, 168, 176, 229, 190, 31, 196, 164, 24, 203, 19, 218, 183, 110, 240, 247, 28, 188, 192, 2, 17, 0, 0, 0, 6, 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