Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38edaeff43e79083394b124dc8343bac3ad3707131b5afadfa2f01e8b52f04dd

Tx prefix hash: 43392863314e920445708a776a0c4fee9e2f4569f194688184b5877987c3bbd1
Tx public key: 0765b26fc1a0b181379bf18cc437470d93376a6b24b8e3c7303a4a86c6ae2d09
Timestamp: 1707101802 Timestamp [UCT]: 2024-02-05 02:56:42 Age [y:d:h:m:s]: 01:065:00:29:03
Block: 950606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307543 RingCT/type: yes/0
Extra: 010765b26fc1a0b181379bf18cc437470d93376a6b24b8e3c7303a4a86c6ae2d090211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0741a9f2b6c819e209bc1c1383b111b48f9d88c4a01dcdce8ea812d3f31230ad 0.600000000000 1409252 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": 950616, "vin": [ { "gen": { "height": 950606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0741a9f2b6c819e209bc1c1383b111b48f9d88c4a01dcdce8ea812d3f31230ad" } } ], "extra": [ 1, 7, 101, 178, 111, 193, 160, 177, 129, 55, 155, 241, 140, 196, 55, 71, 13, 147, 55, 106, 107, 36, 184, 227, 199, 48, 58, 74, 134, 198, 174, 45, 9, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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