Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e7677b87bddfe0e83ee0f6991e58d5911701d56472306b2ea58e13951b7d15b

Tx prefix hash: 6bc3d6f8f56803034b0f41a95139b1fd02b6f68f57dab727fe0c1ac3345a7d24
Tx public key: 104da81c9986726f5b36d9edf459ca6ae8c6db2be33917b36eb8bfb37ca93c7b
Timestamp: 1732639816 Timestamp [UCT]: 2024-11-26 16:50:16 Age [y:d:h:m:s]: 00:205:16:32:00
Block: 1162246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146706 RingCT/type: yes/0
Extra: 01104da81c9986726f5b36d9edf459ca6ae8c6db2be33917b36eb8bfb37ca93c7b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d9a291dda38635243e60298610522c013db258be138d2f3126e7dd521e66fc0 0.600000000000 1647901 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": 1162256, "vin": [ { "gen": { "height": 1162246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d9a291dda38635243e60298610522c013db258be138d2f3126e7dd521e66fc0" } } ], "extra": [ 1, 16, 77, 168, 28, 153, 134, 114, 111, 91, 54, 217, 237, 244, 89, 202, 106, 232, 198, 219, 43, 227, 57, 23, 179, 110, 184, 191, 179, 124, 169, 60, 123, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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