Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cca07ee98b65a33982f2c83b602c0a6621730d0b980e0a01c2d967c446a35b4a

Tx prefix hash: ab6ee01cf217f1a09be968fb275c550f9b2939bc195132e2c5221898506fa153
Tx public key: 99a8c61838c3cf5ad69ec2418f9df7ba45847a579cd11a722e43d959065cd6df
Timestamp: 1719096332 Timestamp [UCT]: 2024-06-22 22:45:32 Age [y:d:h:m:s]: 00:321:02:36:27
Block: 1050045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229500 RingCT/type: yes/0
Extra: 0199a8c61838c3cf5ad69ec2418f9df7ba45847a579cd11a722e43d959065cd6df021100000002c5f9cfd0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84526bedb0530e6da07b3eefed09bb8b9fcc35511abf6b67ae314a09d7b9b4eb 0.600000000000 1520196 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": 1050055, "vin": [ { "gen": { "height": 1050045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84526bedb0530e6da07b3eefed09bb8b9fcc35511abf6b67ae314a09d7b9b4eb" } } ], "extra": [ 1, 153, 168, 198, 24, 56, 195, 207, 90, 214, 158, 194, 65, 143, 157, 247, 186, 69, 132, 122, 87, 156, 209, 26, 114, 46, 67, 217, 89, 6, 92, 214, 223, 2, 17, 0, 0, 0, 2, 197, 249, 207, 208, 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