Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a12ca14efce51c3f47052db28188a79dce887752e8b5e69e2badcd9957de1f9c

Tx prefix hash: 438c9df8c8fffbbad7ae962b1e868b1482476356dbf4949f12d6c9dc4cf55826
Tx public key: 855f614c5c85c0154a911a50b7c35ffafa41b2c2720404069b99cd15c587b62c
Timestamp: 1703631909 Timestamp [UCT]: 2023-12-26 23:05:09 Age [y:d:h:m:s]: 01:342:13:51:52
Block: 921856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503723 RingCT/type: yes/0
Extra: 01855f614c5c85c0154a911a50b7c35ffafa41b2c2720404069b99cd15c587b62c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2d95a149dacee50ef98e8ef88298c88e8b9f279582a8aca0567e013fd51ee69 0.600000000000 1379550 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": 921866, "vin": [ { "gen": { "height": 921856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2d95a149dacee50ef98e8ef88298c88e8b9f279582a8aca0567e013fd51ee69" } } ], "extra": [ 1, 133, 95, 97, 76, 92, 133, 192, 21, 74, 145, 26, 80, 183, 195, 95, 250, 250, 65, 178, 194, 114, 4, 4, 6, 155, 153, 205, 21, 197, 135, 182, 44, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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