Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d1b58b075c8726d97ac94d53827d6e619ceb11f5e477d38ad87372950cea174

Tx prefix hash: 1e5353e8c460adb6ce1dae768139e59e96259bae9a836d373c092782ce1dd53b
Tx public key: d3f35c82045118b09c391f0d9106484b0ecc32217a8cf1f4aa105a45a5282bda
Timestamp: 1714376562 Timestamp [UCT]: 2024-04-29 07:42:42 Age [y:d:h:m:s]: 00:304:22:09:20
Block: 1010935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217950 RingCT/type: yes/0
Extra: 01d3f35c82045118b09c391f0d9106484b0ecc32217a8cf1f4aa105a45a5282bda0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 657da370580e0ee1a7fd69be56fe23fc5a2750e3b887336f8109fcf06541f0c7 0.600000000000 1473021 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": 1010945, "vin": [ { "gen": { "height": 1010935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "657da370580e0ee1a7fd69be56fe23fc5a2750e3b887336f8109fcf06541f0c7" } } ], "extra": [ 1, 211, 243, 92, 130, 4, 81, 24, 176, 156, 57, 31, 13, 145, 6, 72, 75, 14, 204, 50, 33, 122, 140, 241, 244, 170, 16, 90, 69, 165, 40, 43, 218, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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