Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f390a3dd404caf3759584fffaae992f6d7de688ac87c8edbb2a11970297762f9

Tx prefix hash: 0ed93f34aa634d4c998a0e68e517d9cf4c3126df78e8d4b7cb59688ee5fc2191
Tx public key: 30fb7950008a3301f9a9cb9a55577293da046a0f6efbc63d2bd9b2108f100be2
Timestamp: 1699159715 Timestamp [UCT]: 2023-11-05 04:48:35 Age [y:d:h:m:s]: 01:176:11:33:13
Block: 885029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387100 RingCT/type: yes/0
Extra: 0130fb7950008a3301f9a9cb9a55577293da046a0f6efbc63d2bd9b2108f100be2021100000001faf35c9c000000000000000000

1 output(s) for total of 0.717020438000 dcy

stealth address amount amount idx
00: 5e63daf9250ec709d417d5af706f62f463fa87a02319350dc6392a13980338e7 0.717020438000 1340780 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": 885039, "vin": [ { "gen": { "height": 885029 } } ], "vout": [ { "amount": 717020438, "target": { "key": "5e63daf9250ec709d417d5af706f62f463fa87a02319350dc6392a13980338e7" } } ], "extra": [ 1, 48, 251, 121, 80, 0, 138, 51, 1, 249, 169, 203, 154, 85, 87, 114, 147, 218, 4, 106, 15, 110, 251, 198, 61, 43, 217, 178, 16, 143, 16, 11, 226, 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