Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5393e722ded596a4d393d3832eef1fd644c7d6f87575fe2e1071c863427c743

Tx prefix hash: 0d1fb34b0ae55b1b93a2e031825d4cf83e2dc375f2bce1d158bd43dc27ad778d
Tx public key: 069a3839bfec92843412bd61c8c84163439ea716f6813cc43c3b5d8e59ae35d9
Timestamp: 1721803168 Timestamp [UCT]: 2024-07-24 06:39:28 Age [y:d:h:m:s]: 00:251:18:59:03
Block: 1072500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179858 RingCT/type: yes/0
Extra: 01069a3839bfec92843412bd61c8c84163439ea716f6813cc43c3b5d8e59ae35d902110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12463e0d02cc658efd9e30c89991837c6280c3a1b96ddacc674c68a1539238e5 0.600000000000 1544973 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": 1072510, "vin": [ { "gen": { "height": 1072500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12463e0d02cc658efd9e30c89991837c6280c3a1b96ddacc674c68a1539238e5" } } ], "extra": [ 1, 6, 154, 56, 57, 191, 236, 146, 132, 52, 18, 189, 97, 200, 200, 65, 99, 67, 158, 167, 22, 246, 129, 60, 196, 60, 59, 93, 142, 89, 174, 53, 217, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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