Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 892859123804b572281853f216e6e55ee8c9c91bb3e82e8e8b900c086e52b7a6

Tx prefix hash: 601a8da1f26adf2fc244c7faed049ea9b37b2c91fb11494f4676031a8f0ccd0b
Tx public key: e1a80da04a6948cb73fde265577b0933e6779ffd82b05277244a438dc84930ad
Timestamp: 1728612991 Timestamp [UCT]: 2024-10-11 02:16:31 Age [y:d:h:m:s]: 00:171:09:00:16
Block: 1128962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122268 RingCT/type: yes/0
Extra: 01e1a80da04a6948cb73fde265577b0933e6779ffd82b05277244a438dc84930ad02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0aaeb622d6d08324135e643d93674628ea6fbf1fc09f84d3358f45c1abf9722f 0.600000000000 1611785 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": 1128972, "vin": [ { "gen": { "height": 1128962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0aaeb622d6d08324135e643d93674628ea6fbf1fc09f84d3358f45c1abf9722f" } } ], "extra": [ 1, 225, 168, 13, 160, 74, 105, 72, 203, 115, 253, 226, 101, 87, 123, 9, 51, 230, 119, 159, 253, 130, 176, 82, 119, 36, 74, 67, 141, 200, 73, 48, 173, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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