Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2075e6d34fbe92a4915f9e0dd0161d264b815166d64d771d3d3c023212d14c82

Tx prefix hash: b7a8acf289689a1e8822dd6a903b49e1457744ef787920edea23d59bb8b442ea
Tx public key: e127aae52b0d9367b94c6d81fa790e40f34c0e97597c9e28d13deac5cd415e5f
Timestamp: 1695918800 Timestamp [UCT]: 2023-09-28 16:33:20 Age [y:d:h:m:s]: 01:149:00:43:01
Block: 858116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367525 RingCT/type: yes/0
Extra: 01e127aae52b0d9367b94c6d81fa790e40f34c0e97597c9e28d13deac5cd415e5f02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.880451658000 dcy

stealth address amount amount idx
00: 116379f6a1b8344a64106a6b73a9ba1ecbd396b6b4bdd351f33f051cb9e7d53a 0.880451658000 1312280 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": 858126, "vin": [ { "gen": { "height": 858116 } } ], "vout": [ { "amount": 880451658, "target": { "key": "116379f6a1b8344a64106a6b73a9ba1ecbd396b6b4bdd351f33f051cb9e7d53a" } } ], "extra": [ 1, 225, 39, 170, 229, 43, 13, 147, 103, 185, 76, 109, 129, 250, 121, 14, 64, 243, 76, 14, 151, 89, 124, 158, 40, 209, 61, 234, 197, 205, 65, 94, 95, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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