Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be7bcb576765453de47fb05778b451de65894b378816a825d105e4cca3dc7c2f

Tx prefix hash: cf9fdd77e6c451838d7e67203e22cae542bcf8b2f9039cf67509bdaff28a7f6e
Tx public key: 8795a56413e5d8ed881d48760f96ee182f5411fe582e806b4be29c1a75bc90b2
Timestamp: 1700175529 Timestamp [UCT]: 2023-11-16 22:58:49 Age [y:d:h:m:s]: 02:005:00:14:04
Block: 893207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523347 RingCT/type: yes/0
Extra: 018795a56413e5d8ed881d48760f96ee182f5411fe582e806b4be29c1a75bc90b2021100000001faf35c9c000000000000000000

1 output(s) for total of 0.673650156000 dcy

stealth address amount amount idx
00: 9e31d60e9d6b1931cfadf1a625bcabb5da4eb1daff570ce5ce9eb7ddc6ccae5f 0.673650156000 1349370 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": 893217, "vin": [ { "gen": { "height": 893207 } } ], "vout": [ { "amount": 673650156, "target": { "key": "9e31d60e9d6b1931cfadf1a625bcabb5da4eb1daff570ce5ce9eb7ddc6ccae5f" } } ], "extra": [ 1, 135, 149, 165, 100, 19, 229, 216, 237, 136, 29, 72, 118, 15, 150, 238, 24, 47, 84, 17, 254, 88, 46, 128, 107, 75, 226, 156, 26, 117, 188, 144, 178, 2, 17, 0, 0, 0, 1, 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