Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef3657ddce483e824a95b4261697342bd9f1c14d681b6b3fd14ec0d72420173d

Tx prefix hash: 803a0cd15e254cb90d745845cce3d66b95c37788a93d37ba33c410175bf10e42
Tx public key: 5e1d1e41e692c24ece1965ca88e1186c84a0713bc38ba10c1ae7abd79c88e135
Timestamp: 1714249585 Timestamp [UCT]: 2024-04-27 20:26:25 Age [y:d:h:m:s]: 01:219:08:56:30
Block: 1009879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415454 RingCT/type: yes/0
Extra: 015e1d1e41e692c24ece1965ca88e1186c84a0713bc38ba10c1ae7abd79c88e1350211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66ca0045c19e5f6e4da1a2c186b0184edb266aaf22d59e6568642ec70d98f7cb 0.600000000000 1471675 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": 1009889, "vin": [ { "gen": { "height": 1009879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66ca0045c19e5f6e4da1a2c186b0184edb266aaf22d59e6568642ec70d98f7cb" } } ], "extra": [ 1, 94, 29, 30, 65, 230, 146, 194, 78, 206, 25, 101, 202, 136, 225, 24, 108, 132, 160, 113, 59, 195, 139, 161, 12, 26, 231, 171, 215, 156, 136, 225, 53, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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