Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96a9c7a0cc739e6050e250f2bf189e32a6863b468186eee8449e852e51887216

Tx prefix hash: 6c608e6daa4b5b984e5422a13f2c16594727c7d88470c97f8a55ab479b50367f
Tx public key: fb4dac809a2f9474638bd1c21c9f241563223f623abd9a3b4b57f6578481725c
Timestamp: 1709137547 Timestamp [UCT]: 2024-02-28 16:25:47 Age [y:d:h:m:s]: 01:281:05:45:16
Block: 967506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459755 RingCT/type: yes/0
Extra: 01fb4dac809a2f9474638bd1c21c9f241563223f623abd9a3b4b57f6578481725c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: feda23349d6d56961c9eefdd59dc2e2521c06009eed3a3d19adcd0ae19c7f6de 0.600000000000 1427287 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": 967516, "vin": [ { "gen": { "height": 967506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "feda23349d6d56961c9eefdd59dc2e2521c06009eed3a3d19adcd0ae19c7f6de" } } ], "extra": [ 1, 251, 77, 172, 128, 154, 47, 148, 116, 99, 139, 209, 194, 28, 159, 36, 21, 99, 34, 63, 98, 58, 189, 154, 59, 75, 87, 246, 87, 132, 129, 114, 92, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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