Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0240d981e510d43a12290439045cea7af7e66b18091c2c20c89139832589b77d

Tx prefix hash: f38c32ae41fe5dbf008034aa01af45998c49027983ef184ff02d73d37b0c6333
Tx public key: af67a830ad50217a624b65e0628d9d1cef0b88686d6e5a4de91f4c9f511ee6cc
Timestamp: 1706558068 Timestamp [UCT]: 2024-01-29 19:54:28 Age [y:d:h:m:s]: 01:099:18:19:14
Block: 946097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332397 RingCT/type: yes/0
Extra: 01af67a830ad50217a624b65e0628d9d1cef0b88686d6e5a4de91f4c9f511ee6cc02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9fbf3b8ba8b482b8911c529c24de1fec824244e8569668fcce0657d9eda443a 0.600000000000 1404427 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": 946107, "vin": [ { "gen": { "height": 946097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9fbf3b8ba8b482b8911c529c24de1fec824244e8569668fcce0657d9eda443a" } } ], "extra": [ 1, 175, 103, 168, 48, 173, 80, 33, 122, 98, 75, 101, 224, 98, 141, 157, 28, 239, 11, 136, 104, 109, 110, 90, 77, 233, 31, 76, 159, 81, 30, 230, 204, 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