Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7eb98b39a02f615a95c8dde145d158c4c74356281f8dd689929c3e372af01f8

Tx prefix hash: fdf0cc6c512c60839305faff5dda76324e109762528cdef71b347b69fbc7a2a8
Tx public key: 534c76ed8f5808ed75ae33a530d41f64833e52ed3002ae6d3e3d6f7d52e53489
Timestamp: 1738564271 Timestamp [UCT]: 2025-02-03 06:31:11 Age [y:d:h:m:s]: 00:291:17:50:49
Block: 1211018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206287 RingCT/type: yes/0
Extra: 01534c76ed8f5808ed75ae33a530d41f64833e52ed3002ae6d3e3d6f7d52e534890211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 464529b2fad1001dd24fbe7ecc7d12d5995719cfb88dbda6df40d472812059be 0.600000000000 1697773 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": 1211028, "vin": [ { "gen": { "height": 1211018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "464529b2fad1001dd24fbe7ecc7d12d5995719cfb88dbda6df40d472812059be" } } ], "extra": [ 1, 83, 76, 118, 237, 143, 88, 8, 237, 117, 174, 51, 165, 48, 212, 31, 100, 131, 62, 82, 237, 48, 2, 174, 109, 62, 61, 111, 125, 82, 229, 52, 137, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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