Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 675e92e6f3ff0898b515ba62a74d4695d870006766895256cfc44a660987c8a5

Tx prefix hash: eca2b41699f61b3c4e4f6851931a39db7bb3dd6fce071e82fce5d588fb9aac89
Tx public key: a1f6141604cbc50da478c7ceb3e79cda05bbc7aab689c91fe61118f45e2a9f2e
Timestamp: 1710143019 Timestamp [UCT]: 2024-03-11 07:43:39 Age [y:d:h:m:s]: 01:099:08:20:34
Block: 975850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331911 RingCT/type: yes/0
Extra: 01a1f6141604cbc50da478c7ceb3e79cda05bbc7aab689c91fe61118f45e2a9f2e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e07a2ab14da90dd388601374d6764dc038ead2a3b1faaac1a3926aa772cb4bdd 0.600000000000 1435827 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": 975860, "vin": [ { "gen": { "height": 975850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e07a2ab14da90dd388601374d6764dc038ead2a3b1faaac1a3926aa772cb4bdd" } } ], "extra": [ 1, 161, 246, 20, 22, 4, 203, 197, 13, 164, 120, 199, 206, 179, 231, 156, 218, 5, 187, 199, 170, 182, 137, 201, 31, 230, 17, 24, 244, 94, 42, 159, 46, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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