Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8acd692f0152249baa3b66d7f72e34034b9f048bd32749f45ab5e5b0926dcf8d

Tx prefix hash: cd750bf690969ba8bb1e6a3a503de5051f2403c7bb4c898928587d31cf34509b
Tx public key: 8b7c47d9ecb57392331f3dd8e142586983ebb5cce4057cab89a58197ee46de2a
Timestamp: 1734403437 Timestamp [UCT]: 2024-12-17 02:43:57 Age [y:d:h:m:s]: 00:101:00:13:34
Block: 1176873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71961 RingCT/type: yes/0
Extra: 018b7c47d9ecb57392331f3dd8e142586983ebb5cce4057cab89a58197ee46de2a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a9e55dfd6872e2636be30b5dce946f3904de8a6b5bebdb8c70a3b2ea9304681 0.600000000000 1663234 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": 1176883, "vin": [ { "gen": { "height": 1176873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a9e55dfd6872e2636be30b5dce946f3904de8a6b5bebdb8c70a3b2ea9304681" } } ], "extra": [ 1, 139, 124, 71, 217, 236, 181, 115, 146, 51, 31, 61, 216, 225, 66, 88, 105, 131, 235, 181, 204, 228, 5, 124, 171, 137, 165, 129, 151, 238, 70, 222, 42, 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