Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41326ed81005ea9ead703ca624d34bc7797513393faf4f420dcc8342dd0cd13a

Tx prefix hash: 33d170dd52dbe4b9c011b51eeb1fec6732f4ba19ba32c9998ef3c4aa89de7c72
Tx public key: f24d1fd3156a79392fccaf4e46bfbcdc2bed610097d85d2992c5e719b0a384ec
Timestamp: 1725568826 Timestamp [UCT]: 2024-09-05 20:40:26 Age [y:d:h:m:s]: 01:086:15:46:16
Block: 1103725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320386 RingCT/type: yes/0
Extra: 01f24d1fd3156a79392fccaf4e46bfbcdc2bed610097d85d2992c5e719b0a384ec021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87f95da5741e0e33db6e4e39d43a3b708dd8b211d18d6c4cac8bd4e0385ea62a 0.600000000000 1580666 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": 1103735, "vin": [ { "gen": { "height": 1103725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87f95da5741e0e33db6e4e39d43a3b708dd8b211d18d6c4cac8bd4e0385ea62a" } } ], "extra": [ 1, 242, 77, 31, 211, 21, 106, 121, 57, 47, 204, 175, 78, 70, 191, 188, 220, 43, 237, 97, 0, 151, 216, 93, 41, 146, 197, 231, 25, 176, 163, 132, 236, 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