Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca738f23d78d8566cfb5aabf90f21dd2fadcb39ad208ff2a9de4ca08a69a8ba0

Tx prefix hash: b718c26b0d5dfc2fdb8b35fc091a6c3194473d78a428d1e0fc07e9cb81e09fc1
Tx public key: e2b3700c1811ffc99380154f26eb93fd9abdc4cab4d44df38f91c25f34b0b30c
Timestamp: 1699683962 Timestamp [UCT]: 2023-11-11 06:26:02 Age [y:d:h:m:s]: 01:163:04:04:28
Block: 889128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377810 RingCT/type: yes/0
Extra: 01e2b3700c1811ffc99380154f26eb93fd9abdc4cab4d44df38f91c25f34b0b30c021100000003faf35c9c000000000000000000

1 output(s) for total of 0.694944050000 dcy

stealth address amount amount idx
00: 28d87cab4b865aafd6ffd7edf44b6f8252f71c1f0be869cf9463ee6238c94388 0.694944050000 1345105 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": 889138, "vin": [ { "gen": { "height": 889128 } } ], "vout": [ { "amount": 694944050, "target": { "key": "28d87cab4b865aafd6ffd7edf44b6f8252f71c1f0be869cf9463ee6238c94388" } } ], "extra": [ 1, 226, 179, 112, 12, 24, 17, 255, 201, 147, 128, 21, 79, 38, 235, 147, 253, 154, 189, 196, 202, 180, 212, 77, 243, 143, 145, 194, 95, 52, 176, 179, 12, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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