Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebf1a144f96ce1ffb64097f57003fa1311144b37fbe1d7f6faf2ca05bce3fc2e

Tx prefix hash: 155b04158e9e1a1a521ce1b6ef04af6bb5fbe89caf2384f644526fabda4bd6c5
Tx public key: 06940e03e750e281f45bc19c9eac28d5ad36212cd0abd7eebf0c650945cf833d
Timestamp: 1733179525 Timestamp [UCT]: 2024-12-02 22:45:25 Age [y:d:h:m:s]: 00:160:15:22:30
Block: 1166722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114634 RingCT/type: yes/0
Extra: 0106940e03e750e281f45bc19c9eac28d5ad36212cd0abd7eebf0c650945cf833d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8bb11d305e7e80c6b881cca78816403e0932c422ae843fda6891a5ecc37e481 0.600000000000 1652411 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": 1166732, "vin": [ { "gen": { "height": 1166722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8bb11d305e7e80c6b881cca78816403e0932c422ae843fda6891a5ecc37e481" } } ], "extra": [ 1, 6, 148, 14, 3, 231, 80, 226, 129, 244, 91, 193, 156, 158, 172, 40, 213, 173, 54, 33, 44, 208, 171, 215, 238, 191, 12, 101, 9, 69, 207, 131, 61, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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