Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5246e7f172775806b7b56b25e7ea5826515d331a5564c98661eb38e99e93bd28

Tx prefix hash: fcab56ebb0b746407bd98eafd4b7a326555d94f5862af42092d05ef979fe7cd4
Tx public key: 8fce5cda4f466ba95fb0fe42add4679f6a0aec13df1d5e345bb0475293146908
Timestamp: 1744053329 Timestamp [UCT]: 2025-04-07 19:15:29 Age [y:d:h:m:s]: 00:299:19:01:03
Block: 1256460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211923 RingCT/type: yes/0
Extra: 018fce5cda4f466ba95fb0fe42add4679f6a0aec13df1d5e345bb0475293146908021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14126a7cd2d9ac15fb1d99fe3c2ae70faad9015c094873b226d2f392f56b2b2f 0.600000000000 1743573 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": 1256470, "vin": [ { "gen": { "height": 1256460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14126a7cd2d9ac15fb1d99fe3c2ae70faad9015c094873b226d2f392f56b2b2f" } } ], "extra": [ 1, 143, 206, 92, 218, 79, 70, 107, 169, 95, 176, 254, 66, 173, 212, 103, 159, 106, 10, 236, 19, 223, 29, 94, 52, 91, 176, 71, 82, 147, 20, 105, 8, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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