Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ac8c76868eb1a0394c0a355c6bd1f65114f778f6722d22d33409cad9f80f74b

Tx prefix hash: ac2bcee6ffa385c68eac0e0ff934b3cb43003894dce4ffe79d77b14087cb1d8d
Tx public key: 39a7067031ea8e5aaefcc582a91b8e4179ce7dde86c1ac366176c0c42135ef9f
Timestamp: 1726472213 Timestamp [UCT]: 2024-09-16 07:36:53 Age [y:d:h:m:s]: 00:221:04:53:58
Block: 1111206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157944 RingCT/type: yes/0
Extra: 0139a7067031ea8e5aaefcc582a91b8e4179ce7dde86c1ac366176c0c42135ef9f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83c3f963ee1c16c4e11e9c51f36c17510fec57b6af79d38a71dfff2b06a27b7f 0.600000000000 1590085 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": 1111216, "vin": [ { "gen": { "height": 1111206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83c3f963ee1c16c4e11e9c51f36c17510fec57b6af79d38a71dfff2b06a27b7f" } } ], "extra": [ 1, 57, 167, 6, 112, 49, 234, 142, 90, 174, 252, 197, 130, 169, 27, 142, 65, 121, 206, 125, 222, 134, 193, 172, 54, 97, 118, 192, 196, 33, 53, 239, 159, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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