Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50fc1b32d4a478e07c391053beac09ff2b9c45753ba04d886033e05c74d3825e

Tx prefix hash: 6cdf4d2e9617c5e55ebd71e3ca6c8555922ff9c59198e0bd1edcc32a0452cbcc
Tx public key: 172bc6f88d505fef48a45dd941c9cbbbbf42d1931edc8daeaec5b8f9e695c94b
Timestamp: 1698513790 Timestamp [UCT]: 2023-10-28 17:23:10 Age [y:d:h:m:s]: 01:165:08:22:05
Block: 879639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379172 RingCT/type: yes/0
Extra: 01172bc6f88d505fef48a45dd941c9cbbbbf42d1931edc8daeaec5b8f9e695c94b02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.747120840000 dcy

stealth address amount amount idx
00: df9e7408433ec1954a1b5265beb262b9a9de1bd2102e4b1e6fc7760ac85a757f 0.747120840000 1335173 of 0

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": 879649, "vin": [ { "gen": { "height": 879639 } } ], "vout": [ { "amount": 747120840, "target": { "key": "df9e7408433ec1954a1b5265beb262b9a9de1bd2102e4b1e6fc7760ac85a757f" } } ], "extra": [ 1, 23, 43, 198, 248, 141, 80, 95, 239, 72, 164, 93, 217, 65, 201, 203, 187, 191, 66, 209, 147, 30, 220, 141, 174, 174, 197, 184, 249, 230, 149, 201, 75, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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