Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c051a3b7ae93778dcb874d93800329448c161fed3b7c2d1bb3aa3bcd6cc38937

Tx prefix hash: 6fd4944a1dd9e8005a7c60cb01be1f4323586fa103de94c1233eedfd0b69c16a
Tx public key: 84bfbe811ce1e455b179b6ec77b5217f1dfb90d27db2cde681c9e6b12ff8a3c1
Timestamp: 1708973500 Timestamp [UCT]: 2024-02-26 18:51:40 Age [y:d:h:m:s]: 01:107:04:44:09
Block: 966148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337633 RingCT/type: yes/0
Extra: 0184bfbe811ce1e455b179b6ec77b5217f1dfb90d27db2cde681c9e6b12ff8a3c102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e704ca4f47b39dd9a58e182e916c2b80c7fc0c46f0b17aafd4053c2dab9889d8 0.600000000000 1425905 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": 966158, "vin": [ { "gen": { "height": 966148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e704ca4f47b39dd9a58e182e916c2b80c7fc0c46f0b17aafd4053c2dab9889d8" } } ], "extra": [ 1, 132, 191, 190, 129, 28, 225, 228, 85, 177, 121, 182, 236, 119, 181, 33, 127, 29, 251, 144, 210, 125, 178, 205, 230, 129, 201, 230, 177, 47, 248, 163, 193, 2, 17, 0, 0, 0, 5, 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