Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 197d629a0fa051e268de8d30dfa5ba9de20071a51c262de787cce6388490fa5c

Tx prefix hash: 5e8cb6bb7cc5885e2f749922210be4e902b09fa6e6a64d43f40970bb8883a046
Tx public key: 81266704ed70e5f8e21d5b09ba924a35c4650e7fa6f150a3fff4c5fd60ba3d11
Timestamp: 1724213247 Timestamp [UCT]: 2024-08-21 04:07:27 Age [y:d:h:m:s]: 00:268:20:06:09
Block: 1092496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192019 RingCT/type: yes/0
Extra: 0181266704ed70e5f8e21d5b09ba924a35c4650e7fa6f150a3fff4c5fd60ba3d11021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46bab96596613e49c4acd5d3165518d03684167073d84fa3442e0536e1cfb3ff 0.600000000000 1567253 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": 1092506, "vin": [ { "gen": { "height": 1092496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46bab96596613e49c4acd5d3165518d03684167073d84fa3442e0536e1cfb3ff" } } ], "extra": [ 1, 129, 38, 103, 4, 237, 112, 229, 248, 226, 29, 91, 9, 186, 146, 74, 53, 196, 101, 14, 127, 166, 241, 80, 163, 255, 244, 197, 253, 96, 186, 61, 17, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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