Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee7fe2a92575925986e63a679ecc053a11b4d221435a159bb271bff623d4d95e

Tx prefix hash: 8176602212f9d924cd613492c7d6cd2bfa3780d74b8ccd49e6cc9db0ae859864
Tx public key: ec3ae03b89a6b9f0ca8082bd22a4fd7ce387908bb4d38861f163214ac1dc4fe4
Timestamp: 1709348298 Timestamp [UCT]: 2024-03-02 02:58:18 Age [y:d:h:m:s]: 00:243:12:22:12
Block: 969250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174347 RingCT/type: yes/0
Extra: 01ec3ae03b89a6b9f0ca8082bd22a4fd7ce387908bb4d38861f163214ac1dc4fe40211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54666d9f373d4819e0ffc566794e4aff5f02c8aad27d99563a450a28433b74be 0.600000000000 1429079 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": 969260, "vin": [ { "gen": { "height": 969250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54666d9f373d4819e0ffc566794e4aff5f02c8aad27d99563a450a28433b74be" } } ], "extra": [ 1, 236, 58, 224, 59, 137, 166, 185, 240, 202, 128, 130, 189, 34, 164, 253, 124, 227, 135, 144, 139, 180, 211, 136, 97, 241, 99, 33, 74, 193, 220, 79, 228, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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