Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc7d334f9eebc3de1e3db741c31039c90252cd620ce57b95369c675f83396e7

Tx prefix hash: 8aaf5e675c48af5007d8c075a60d4eb9b71d6f71ef7a37fc38a4bb7ed04e80bd
Tx public key: 35fc8a6efe778e0128fb9884b321ede11db3ae7db32c9ba4f236ba95d2c8c339
Timestamp: 1737840659 Timestamp [UCT]: 2025-01-25 21:30:59 Age [y:d:h:m:s]: 00:143:03:10:35
Block: 1205265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102037 RingCT/type: yes/0
Extra: 0135fc8a6efe778e0128fb9884b321ede11db3ae7db32c9ba4f236ba95d2c8c339021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dab9e10077dbb10c85a0481c7ea6822d2a5af073887914fba6e3e10b0f49715 0.600000000000 1691962 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": 1205275, "vin": [ { "gen": { "height": 1205265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dab9e10077dbb10c85a0481c7ea6822d2a5af073887914fba6e3e10b0f49715" } } ], "extra": [ 1, 53, 252, 138, 110, 254, 119, 142, 1, 40, 251, 152, 132, 179, 33, 237, 225, 29, 179, 174, 125, 179, 44, 155, 164, 242, 54, 186, 149, 210, 200, 195, 57, 2, 17, 0, 0, 0, 4, 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