Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 044fa19b554ccdb8c0a1480101c7604a812e9637c1b8b28605faa1ab476fc090

Tx prefix hash: e763925eb88795357727c75b3e1c125e9152f636ed8b958fbac38d499c432fc9
Tx public key: 7fd7aa7b608b7a09df1ceb3c968035d02bb1551d35f6ebad43211e03a8c89ccf
Timestamp: 1714300737 Timestamp [UCT]: 2024-04-28 10:38:57 Age [y:d:h:m:s]: 00:343:19:36:14
Block: 1010304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245767 RingCT/type: yes/0
Extra: 017fd7aa7b608b7a09df1ceb3c968035d02bb1551d35f6ebad43211e03a8c89ccf02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2559f1fa1b69ada4c97fdcd3a5cce05ea9702ffd71b626f7940619158add5433 0.600000000000 1472218 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": 1010314, "vin": [ { "gen": { "height": 1010304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2559f1fa1b69ada4c97fdcd3a5cce05ea9702ffd71b626f7940619158add5433" } } ], "extra": [ 1, 127, 215, 170, 123, 96, 139, 122, 9, 223, 28, 235, 60, 150, 128, 53, 208, 43, 177, 85, 29, 53, 246, 235, 173, 67, 33, 30, 3, 168, 200, 156, 207, 2, 17, 0, 0, 0, 2, 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