Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4de0b2e7946a23bbb3f19c2c7c56d36fe9e4ecca7bcf01edc7fdf1e331cf6e89

Tx prefix hash: eeda5a18512d996127efd5891b042406b172281ad33a422ffd49e7e1c9d05319
Tx public key: ca6b4e57adf18fb9a8b170fb428ff047614c9c869ecf4fe31742553edacf239a
Timestamp: 1733111354 Timestamp [UCT]: 2024-12-02 03:49:14 Age [y:d:h:m:s]: 00:122:07:51:29
Block: 1166156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87222 RingCT/type: yes/0
Extra: 01ca6b4e57adf18fb9a8b170fb428ff047614c9c869ecf4fe31742553edacf239a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e61a1a35ea749122790c1c0b37170de739a6e056439109e021a0bea089fb79ae 0.600000000000 1651833 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": 1166166, "vin": [ { "gen": { "height": 1166156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e61a1a35ea749122790c1c0b37170de739a6e056439109e021a0bea089fb79ae" } } ], "extra": [ 1, 202, 107, 78, 87, 173, 241, 143, 185, 168, 177, 112, 251, 66, 143, 240, 71, 97, 76, 156, 134, 158, 207, 79, 227, 23, 66, 85, 62, 218, 207, 35, 154, 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