Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bee4cec1cb7d2168df3a5d21094371f1d3a2277d79ab4e45f5550a7b3de4933

Tx prefix hash: 544f841c7bfcc9240e434f6871ce9f74ea0ec3f943362eca7880a3b7cd2b7b5b
Tx public key: e0469135223bcffa6504148d26a656ccefc7a2ff1490ac11cb747d27294191f0
Timestamp: 1726141087 Timestamp [UCT]: 2024-09-12 11:38:07 Age [y:d:h:m:s]: 01:057:16:23:15
Block: 1108459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299651 RingCT/type: yes/0
Extra: 01e0469135223bcffa6504148d26a656ccefc7a2ff1490ac11cb747d27294191f002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8e62bf6347b3d6d58ebe3c6a340f60dca2d1dbd78fa8e580ba0f2fcfd0c6a87 0.600000000000 1586364 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": 1108469, "vin": [ { "gen": { "height": 1108459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8e62bf6347b3d6d58ebe3c6a340f60dca2d1dbd78fa8e580ba0f2fcfd0c6a87" } } ], "extra": [ 1, 224, 70, 145, 53, 34, 59, 207, 250, 101, 4, 20, 141, 38, 166, 86, 204, 239, 199, 162, 255, 20, 144, 172, 17, 203, 116, 125, 39, 41, 65, 145, 240, 2, 17, 0, 0, 0, 5, 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