Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1eadd8774a866afab38c60e503d823e3b8c4fba8b4260768bff62fdc9de6b3f

Tx prefix hash: 5a0ce86ad32007b6c0d1dd6241661e84e1a6aaf7b9c4cd426660c11995430ad1
Tx public key: f984ebe40eda169b25edcb91dfe4abf9c49844ad2d316c8e8be21b294e6e5f7f
Timestamp: 1734331398 Timestamp [UCT]: 2024-12-16 06:43:18 Age [y:d:h:m:s]: 00:011:07:50:33
Block: 1176276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8082 RingCT/type: yes/0
Extra: 01f984ebe40eda169b25edcb91dfe4abf9c49844ad2d316c8e8be21b294e6e5f7f0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd2ee9202a276c35f0cec4723d7c507eb5cb60d4471a95c71f4c37ed77cbaab8 0.600000000000 1662607 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": 1176286, "vin": [ { "gen": { "height": 1176276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd2ee9202a276c35f0cec4723d7c507eb5cb60d4471a95c71f4c37ed77cbaab8" } } ], "extra": [ 1, 249, 132, 235, 228, 14, 218, 22, 155, 37, 237, 203, 145, 223, 228, 171, 249, 196, 152, 68, 173, 45, 49, 108, 142, 139, 226, 27, 41, 78, 110, 95, 127, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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