Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68ee45f5db1c4270f18018efcd4b3fa36e7c4307e5d95d936c0e40268b27febc

Tx prefix hash: 16836de3b5b060c8f79add22bc93a6d32adaa6e11e41d89748f8c93203086623
Tx public key: 505cf9030388abeba3da9eed512ea56a0d1bbc68b89b22decc8d14bc8375fe8d
Timestamp: 1713382612 Timestamp [UCT]: 2024-04-17 19:36:52 Age [y:d:h:m:s]: 01:200:11:17:37
Block: 1002687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401938 RingCT/type: yes/0
Extra: 01505cf9030388abeba3da9eed512ea56a0d1bbc68b89b22decc8d14bc8375fe8d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e24c178acb1d782bb4a7e9230eaea85d4878915c120629f97f2f74f5d39a14f6 0.600000000000 1463207 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": 1002697, "vin": [ { "gen": { "height": 1002687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e24c178acb1d782bb4a7e9230eaea85d4878915c120629f97f2f74f5d39a14f6" } } ], "extra": [ 1, 80, 92, 249, 3, 3, 136, 171, 235, 163, 218, 158, 237, 81, 46, 165, 106, 13, 27, 188, 104, 184, 155, 34, 222, 204, 141, 20, 188, 131, 117, 254, 141, 2, 17, 0, 0, 0, 4, 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