Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7ce7a3332ae07d7c049273db25bce47ad0f0c2e197a6529835291fe3f59d843

Tx prefix hash: 5e7e19bce6cbe0aa9b4e9223d9b3d4fa41324a3b95584d17d4cd9341bd630ff7
Tx public key: f8295f6fd9f2b8630afacb1d4fc33cec95af2f13f2f858d90b39fe2badedb00d
Timestamp: 1702949171 Timestamp [UCT]: 2023-12-19 01:26:11 Age [y:d:h:m:s]: 01:330:22:32:04
Block: 916192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495386 RingCT/type: yes/0
Extra: 01f8295f6fd9f2b8630afacb1d4fc33cec95af2f13f2f858d90b39fe2badedb00d02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 493d7f7286dc3f2ebb1bb59b2c477921509b7364962d49fb7c9674c616f4379b 0.600000000000 1373674 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": 916202, "vin": [ { "gen": { "height": 916192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "493d7f7286dc3f2ebb1bb59b2c477921509b7364962d49fb7c9674c616f4379b" } } ], "extra": [ 1, 248, 41, 95, 111, 217, 242, 184, 99, 10, 250, 203, 29, 79, 195, 60, 236, 149, 175, 47, 19, 242, 248, 88, 217, 11, 57, 254, 43, 173, 237, 176, 13, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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